Triple
T37331506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stage Manager (Our Town) |
E926762
|
entity |
| Predicate | canStepInAsMinorCharacters |
P132007
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Stage Manager (Our Town), canStepInAsMinorCharacters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canStepInAsMinorCharacters Context triple: [Stage Manager (Our Town), canStepInAsMinorCharacters, true]
-
A.
isMinor
Indicates that one entity is legally or socially considered underage or not yet an adult in relation to a given context.
-
B.
isMinorFigureIn
chosen
Indicates that an entity plays a small, secondary, or relatively insignificant role within another entity, such as a work, event, or context.
-
C.
isAdultCharacter
Indicates that a character has reached adulthood, typically meeting the age or maturity criteria defining an adult within the given context.
-
D.
hasGuardianCharacter
Indicates that one entity serves as a guardian or protective character for another entity.
-
E.
leadCharacterHasChild
Indicates that the lead character is the parent of the specified child.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.