Triple
T8399975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red and Blue Chair |
E198146
|
entity |
| Predicate | laterProduction |
P82027
|
FINISHED |
| Object | manufactured in licensed editions |
—
|
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: manufactured in licensed editions | Statement: [Red and Blue Chair, laterProduction, manufactured in licensed editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterProduction Context triple: [Red and Blue Chair, laterProduction, manufactured in licensed editions]
-
A.
laterProducedIn
Indicates that one production event or version occurred after another in time.
-
B.
laterProducedBy
Indicates that something is produced or created by an entity at a later time than some referenced or implied production event.
-
C.
laterReleased
Indicates that one entity was released at a time chronologically after the release of another entity.
-
D.
previousProduction
Indicates that one production event, item, or version occurred or was created before another in a sequence.
-
E.
laterProductType
Indicates that one product type occurs or is introduced after another product type in time or sequence.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb824bfcbc8190b26bfcb5f8c4777c |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:04 p.m.