Triple
T763463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC North |
E16121
|
entity |
| Predicate | foundedAsCurrentConfiguration |
P18933
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [NFC North, foundedAsCurrentConfiguration, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCurrentConfiguration Context triple: [NFC North, foundedAsCurrentConfiguration, 2002]
-
A.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
hasFoundation
Indicates that an entity is supported, established, or based upon a particular foundation or underlying basis.
-
C.
foundedAsPartOf
Indicates that an entity was established as a component, division, or subset of a larger existing organization, project, or structure.
-
D.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
E.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a69c8c448190a036a04fd8fdd2c2 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a506106081909ef97a679ff00a5a |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a5a35c68819082429755c046e9a7 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.