Triple
T22932284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EInfo |
E569471
|
entity |
| Predicate | outputElement |
P66288
|
FINISHED |
| Object | DbInfo |
—
|
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: DbInfo | Statement: [EInfo, outputElement, DbInfo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputElement Context triple: [EInfo, outputElement, DbInfo]
-
A.
outputIs
Indicates that one entity functions as the result, product, or outcome produced by another entity or process.
-
B.
outputOf
chosen
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
C.
mainElement
Indicates that one entity is the primary or most important component within another entity or structure.
-
D.
outputProperty
Indicates that a property or attribute is produced, exposed, or yielded as the output of a process, function, or system.
-
E.
outputsTo
Indicates that the result or data produced by one entity is directed or sent to another entity as its destination or target.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813260608190bb9e1ca704c7e12f |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.