Triple
T9737915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CZ P-07 |
E236109
|
entity |
| Predicate | hasFinishOption |
P61829
|
FINISHED |
| Object | polymer frame in black |
—
|
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: polymer frame in black | Statement: [CZ P-07, hasFinishOption, polymer frame in black]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinishOption Context triple: [CZ P-07, hasFinishOption, polymer frame in black]
-
A.
hasFinishingMove
Indicates that one entity possesses or is associated with a specific, often decisive or signature, final action or move used to conclude an encounter or event.
-
B.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
C.
finishOptions
chosen
Indicates that one entity specifies or controls the possible ways in which another entity can be completed, finalized, or brought to an end.
-
D.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
-
E.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef2ba048190811d6f4251fdb270 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.