Triple
T37994977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Beginning |
E947922
|
entity |
| Predicate | hasMainPerformerBirthName |
P27232
|
FINISHED |
| Object | Jaime Luis Gomez |
E280628
|
NE 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: Jaime Luis Gomez | Statement: [The Beginning, hasMainPerformerBirthName, Jaime Luis Gomez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPerformerBirthName Context triple: [The Beginning, hasMainPerformerBirthName, Jaime Luis Gomez]
-
A.
performerBirthName
chosen
Indicates the full name a performer was given at birth, as distinct from any stage or professional name they may use.
-
B.
hasPerformerGivenName
Indicates that a performer is associated with a specific given (first) name.
-
C.
performerFullName
Indicates the complete name of the entity that performs an action or role in the described context.
-
D.
hasPerformerBirthYear
Indicates that a performer is associated with a specific year in which they were born.
-
E.
hasMainPerformerOccupation
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional role.
- F. None of above.
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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42ca7f3b4c8190a1a1422da434124c |
completed | June 29, 2026, 7:41 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.