Triple
T29320637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sethu |
E743504
|
entity |
| Predicate | launchedDirectorCareerOf |
P14805
|
FINISHED |
| Object | Bala |
—
|
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: Bala | Statement: [Sethu, launchedDirectorCareerOf, Bala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedDirectorCareerOf Context triple: [Sethu, launchedDirectorCareerOf, Bala]
-
A.
launchedCareerOf
chosen
Indicates that one entity’s actions, support, or involvement initiated or significantly advanced another entity’s professional career.
-
B.
workedAsDirectorFor
Indicates that one entity held the role of director in relation to another entity, such as an organization, project, or production.
-
C.
positionInDirectorsCareer
Indicates the specific point or rank that a work or event occupies within the chronological sequence of a director’s professional career.
-
D.
startedActingCareer
Indicates that an entity began their professional work or involvement in acting at a specific time or event.
-
E.
partOfCreativeCareerOf
Indicates that one entity represents a work, role, or activity that forms a component or phase within another entity’s overall creative career.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 1:23 p.m.