Triple
T1917212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halifax |
E40044
|
entity |
| Predicate | hasTextileHeritage |
P2411
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Halifax, hasTextileHeritage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTextileHeritage Context triple: [Halifax, hasTextileHeritage, true]
-
A.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
B.
retainsHeritageOf
Indicates that one entity preserves, maintains, or keeps alive the cultural, historical, or traditional legacy originating from another entity.
-
C.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
-
D.
hasIndustrialHeritage
chosen
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
-
E.
combinesHeritageOf
Indicates a relationship where one entity integrates or unites the cultural, ancestral, or historical heritage of two or more other entities into a combined whole.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb20f54848190b9457e1231aa49db |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.