Triple
T25958491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Times universe |
E645467
|
entity |
| Predicate | setInTypeOfLocation |
P104439
|
FINISHED |
| Object | public housing project |
—
|
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: public housing project | Statement: [Good Times universe, setInTypeOfLocation, public housing project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInTypeOfLocation Context triple: [Good Times universe, setInTypeOfLocation, public housing project]
-
A.
settingLocationType
chosen
Indicates the type or category of location in which an event, action, or situation takes place.
-
B.
subjectLocationType
Indicates the type or category of location associated with the subject in the relationship.
-
C.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
-
D.
setLocation
Indicates assigning or updating the place or position where an entity is located.
-
E.
definesLocation
Indicates that one entity specifies or establishes the spatial or geographic position of another entity.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604a1294c81908d60fb46f45adab7 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:47 a.m.