Triple
T9742368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spotlight |
E236216
|
entity |
| Predicate | relationToOtherSections |
P37
|
FINISHED |
| Object | distinct from U.S. Dramatic Competition |
—
|
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: distinct from U.S. Dramatic Competition | Statement: [Spotlight, relationToOtherSections, distinct from U.S. Dramatic Competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToOtherSections Context triple: [Spotlight, relationToOtherSections, distinct from U.S. Dramatic Competition]
-
A.
relationshipToSectionVIII
Indicates the nature or type of connection an entity has to Section VIII within a larger structure, document, or framework.
-
B.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
associatedWithSection
Indicates that one entity is linked or connected to a particular section within a larger structure or context.
-
D.
relatedBlock
Indicates that one block is associated with or connected to another block in some relevant way.
-
E.
sharesSectionsWith
Indicates that two entities have one or more sections or segments in common.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f2cb7008190a829a03114d6c704 |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.