Triple
T28615598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LineTo |
E724265
|
entity |
| Predicate | usesCurrentObject |
P180026
|
FINISHED |
| Object | current pen |
—
|
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: current pen | Statement: [LineTo, usesCurrentObject, current pen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCurrentObject Context triple: [LineTo, usesCurrentObject, current pen]
-
A.
usesFoundObject
Indicates that an entity makes use of an object that it has previously found or discovered.
-
B.
usesReferenceObjects
Indicates that an entity performs an action or makes a determination by relying on one or more other entities as reference points or benchmarks.
-
C.
usesCurrentCollectionMethod
Indicates that an entity performs or relies on the collection method that is currently in use or officially designated as the standard.
-
D.
usesOriginalObject
Indicates that an entity performs an action or function by directly employing the initial, unmodified object rather than a copy, derivative, or replacement.
-
E.
includesCurrentOf
Indicates that one entity encompasses or contains the present or ongoing state, value, or flow associated with another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 28, 2026, 4:31 a.m.