Triple
T30683100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syrtos |
E781108
|
entity |
| Predicate | isOftenLedBy |
P18413
|
FINISHED |
| Object | lead dancer at the right end of the line |
—
|
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: lead dancer at the right end of the line | Statement: [Syrtos, isOftenLedBy, lead dancer at the right end of the line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenLedBy Context triple: [Syrtos, isOftenLedBy, lead dancer at the right end of the line]
-
A.
leaderIsUsually
chosen
Indicates that an entity typically serves as the leader in relation to another entity or within a given context.
-
B.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
C.
wirdGeleitetVon
Indicates that something (such as an organization, project, or process) is being led or directed by a specific person or entity.
-
D.
shapedByLeader
Indicates that something’s form, direction, or characteristics are determined or significantly influenced by a particular leader.
-
E.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:33 p.m.