Triple
T17511195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born for Greatness |
E426451
|
entity |
| Predicate | hasLiveUse |
P127710
|
FINISHED |
| Object | performed at concerts |
—
|
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: performed at concerts | Statement: [Born for Greatness, hasLiveUse, performed at concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveUse Context triple: [Born for Greatness, hasLiveUse, performed at concerts]
-
A.
hasPresentUse
Indicates that an entity is currently being used or serving a particular function at the present time.
-
B.
hasLowerLevelUse
Indicates that one entity is used or applied at a more detailed, specific, or subordinate level within the context of another entity’s use.
-
C.
hasAdjacentUse
Indicates that one entity is used or occurs directly next to another in space, time, or sequence.
-
D.
hasLivingComponents
Indicates that an entity includes or is composed of one or more living or biological components.
-
E.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4525c21c88190a9394c4bce006a38 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:48 a.m.