Triple
T36958390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvester |
E914244
|
entity |
| Predicate | mapRequirement |
P87442
|
FINISHED |
| Object | maps with team bases and central area |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: maps with team bases and central area | Statement: [Harvester, mapRequirement, maps with team bases and central area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapRequirement Context triple: [Harvester, mapRequirement, maps with team bases and central area]
-
A.
mappingRequirement
Indicates that one entity must be mapped or corresponded to another entity according to a specified rule, condition, or constraint.
-
B.
mapMustComplyWith
chosen
Indicates that a given map is required to adhere to specified rules, constraints, or standards.
-
C.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
-
D.
mapsIncluded
Indicates that one map or mapping is contained within, or is a subset of, another map or mapping.
-
E.
mapSystem
Indicates a relationship where one system is associated with or represented by a specific map or mapping framework.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.