Triple
T34724411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNXN |
E1001015
|
entity |
| Predicate | stageNameChangeFrom |
P181555
|
FINISHED |
| Object | Buju |
—
|
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: Buju | Statement: [BNXN, stageNameChangeFrom, Buju]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageNameChangeFrom Context triple: [BNXN, stageNameChangeFrom, Buju]
-
A.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
B.
stageNameDerivedFrom
Indicates that an entity’s stage name is derived from, based on, or taken from another specified name or source.
-
C.
stageNameDuringRelease
Indicates the stage name an entity used specifically during the time of a particular release.
-
D.
scriptStageOf
Indicates that something represents a particular stage or step within the overall structure or progression of a script.
-
E.
usedStageNameUntil
Indicates that an entity used a particular stage name up to a specified point in time, after which it was no longer used.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.