Triple
T23546705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N.O.R.E. |
E577913
|
entity |
| Predicate | mainPerformerLaterKnownAs |
P68993
|
FINISHED |
| Object | N.O.R.E. |
—
|
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: N.O.R.E. | Statement: [N.O.R.E., mainPerformerLaterKnownAs, N.O.R.E.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformerLaterKnownAs Context triple: [N.O.R.E., mainPerformerLaterKnownAs, N.O.R.E.]
-
A.
laterPerformerName
chosen
Indicates that an entity’s name refers to a performer who took on a role or performance at a later time than another performer associated with the same context or work.
-
B.
mainPerformerCurrentName
Indicates that the referenced name is the current official or primary name of the main performer associated with an event or work.
-
C.
performerBirthName
Indicates the full name a performer was given at birth, as distinct from any stage or professional name they may use.
-
D.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
E.
performerFullName
Indicates the complete name of the entity that performs an action or role in the described context.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecb567c8190a54d2c3b63282af5 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.