Triple
T666727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tap Hus |
E12879
|
entity |
| Predicate | hasCapitalRole |
P18085
|
FINISHED |
| Object | capital of the Danish West Indies |
—
|
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: capital of the Danish West Indies | Statement: [Tap Hus, hasCapitalRole, capital of the Danish West Indies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalRole Context triple: [Tap Hus, hasCapitalRole, capital of the Danish West Indies]
-
A.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
B.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
C.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
D.
hasPoliticalRole
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or context.
-
E.
hasChiefExecutiveRole
Indicates that an entity holds the highest executive leadership position and overall managerial authority within an organization.
- F. None of above. chosen
Provenance (4 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ff7ca788190bef58ce46849b9d0 |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49fcf0cb4819096edea4037ca2c03 |
completed | March 1, 2026, 8:21 p.m. |
Created at: March 1, 2026, 7:36 p.m.