Triple
T26876427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBS |
E676762
|
entity |
| Predicate | hasExecutiveCharacter |
P169926
|
FINISHED |
| Object | Jordan McDeere |
—
|
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: Jordan McDeere | Statement: [NBS, hasExecutiveCharacter, Jordan McDeere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExecutiveCharacter Context triple: [NBS, hasExecutiveCharacter, Jordan McDeere]
-
A.
hasExecutiveAuthority
Indicates that one entity holds formal decision-making and managerial power over an organization, group, or process.
-
B.
haveExecutiveHead
Indicates that one entity serves as the executive leader or chief authority (e.g., CEO, president, head of government) of another entity.
-
C.
hasExecutiveHeadTitle
Indicates the official job title held by the person who serves as the executive head of an organization or entity.
-
D.
hasNationalExecutive
Indicates that an entity possesses or is associated with a national-level executive authority or governing body.
-
E.
hasExecutiveSeat
Indicates that an entity holds a position or seat with executive authority or decision-making power within an organization or governing body.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 27, 2026, 5:36 a.m.