Triple
T8056594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be Best |
E188016
|
entity |
| Predicate | successorInitiativeBySamePerson |
P9224
|
FINISHED |
| Object | Fostering the Future |
—
|
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: Fostering the Future | Statement: [Be Best, successorInitiativeBySamePerson, Fostering the Future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInitiativeBySamePerson Context triple: [Be Best, successorInitiativeBySamePerson, Fostering the Future]
-
A.
hasCorporateSuccessor
Indicates that one corporate entity is the legal successor to another, inheriting its rights, obligations, or continuity of business.
-
B.
successorRole
Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
-
C.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
D.
successorProject
Indicates that one project directly follows and continues or replaces another project in sequence.
-
E.
successorCampaign
chosen
Indicates that one campaign directly follows and continues or replaces another campaign in sequence.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fa26fb88190b6799bddeb68ed78 |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.