Triple
T36271691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin |
E892688
|
entity |
| Predicate | usesFinishType |
P185082
|
FINISHED |
| Object | nitrocellulose lacquer |
—
|
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: nitrocellulose lacquer | Statement: [Martin, usesFinishType, nitrocellulose lacquer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFinishType Context triple: [Martin, usesFinishType, nitrocellulose lacquer]
-
A.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
B.
startFinishType
Indicates the specific way in which an activity, event, or process begins and/or ends (e.g., its initiation and completion characteristics).
-
C.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
D.
oftenFinishedWith
Indicates that one action, event, or process is frequently concluded or brought to an end by another specified action, event, or process.
-
E.
useEnded
Indicates that an entity’s period of using or employing another entity has come to an end.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.