Triple
T29021030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisa's Substitute |
E737450
|
entity |
| Predicate | guestStarCredit |
P45889
|
FINISHED |
| Object | Sam Etic |
—
|
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: Sam Etic | Statement: [Lisa's Substitute, guestStarCredit, Sam Etic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guestStarCredit Context triple: [Lisa's Substitute, guestStarCredit, Sam Etic]
-
A.
guestStar
chosen
Indicates that one entity appears in a limited, special, or featured role within another entity’s production, event, or context, without being a regular or primary participant.
-
B.
hostStar
Indicates that one celestial object serves as the primary star around which another object, such as a planet or system, is associated or orbits.
-
C.
guestOnBoard
Indicates that an entity is currently present as a guest aboard a vehicle, vessel, or similar conveyance.
-
D.
creditsAre
Indicates that certain credits are assigned, attributed, or owed to a particular entity or set of entities.
-
E.
creditsCanBe
Indicates that certain credits are permitted to be in a specified state, category, or usage condition.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66005ea00819085501231fe82cc5e |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:49 a.m.