Triple
T19533334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | That Way |
E488707
|
entity |
| Predicate | isStandaloneSingle |
P88709
|
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: [That Way, isStandaloneSingle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandaloneSingle Context triple: [That Way, isStandaloneSingle, true]
-
A.
isStandaloneWork
Indicates that a work exists independently and is not part of a larger series, collection, or multi-part work.
-
B.
isSingle
Indicates that an entity is not currently in a romantic relationship or legally married.
-
C.
isStandaloneFriendly
Indicates that an entity can operate or be used effectively on its own without requiring integration or support from other entities.
-
D.
isStandaloneRelease
chosen
Indicates that the release exists independently and is not part of a larger collection, series, or bundled set.
-
E.
standaloneWithinSeries
Indicates that an item is part of a larger series but is intended to function independently and be understandable on its own, without requiring direct reliance on other parts of the series.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6364091f4819088b27d0ffdf6010d |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.