Triple
T29341571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthem |
E744049
|
entity |
| Predicate | hasHubLocation |
P104352
|
FINISHED |
| Object | Fort Tarsis |
—
|
NE NERFINISHED |
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: Fort Tarsis | Statement: [Anthem, hasHubLocation, Fort Tarsis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHubLocation Context triple: [Anthem, hasHubLocation, Fort Tarsis]
-
A.
hasFacilityLocation
Indicates that an entity possesses or is associated with a facility situated at a specific location.
-
B.
Global HubLocation
Indicates a location that serves as a central, primary hub for global operations, connections, or activities.
-
C.
locatedInHubOf
Indicates that one entity is situated within the central hub or core area associated with another entity.
-
D.
hasMajorHubIn
chosen
Indicates that an entity maintains a primary or significant operational hub or center in a specified location.
-
E.
hasTrialLocation
Indicates that a trial or legal proceeding takes place at, or is associated with, a specific location.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 1:34 p.m.