Triple
T25729327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Star Playhouse |
E645194
|
entity |
| Predicate | hasStarSystem |
P175288
|
FINISHED |
| Object | rotating lead actors |
—
|
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: rotating lead actors | Statement: [Four Star Playhouse, hasStarSystem, rotating lead actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStarSystem Context triple: [Four Star Playhouse, hasStarSystem, rotating lead actors]
-
A.
isInPlanetarySystem
Indicates that one celestial object is located within and belongs to a particular planetary system.
-
B.
isMultipleStarSystem
Indicates that a star system contains two or more stars gravitationally bound together, rather than a single isolated star.
-
C.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
-
D.
starSystem
Indicates a relationship where an astronomical object or location belongs to, is part of, or is located within a particular star system.
-
E.
capitalStarSystem
Indicates that a star system serves as the primary or capital system for a given political or organizational entity.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 21, 2026, 11:10 p.m.