Triple
T22814283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manifest V2 |
E565060
|
entity |
| Predicate | hasKeyField |
P149837
|
FINISHED |
| Object | manifest_version |
—
|
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: manifest_version | Statement: [Manifest V2, hasKeyField, manifest_version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyField Context triple: [Manifest V2, hasKeyField, manifest_version]
-
A.
hasKeyCol
Indicates that one entity serves as the key column (or set of key columns) used to uniquely identify or index records in another entity, such as a table or dataset.
-
B.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
C.
hasKeyDimension
Indicates that one entity possesses or defines a primary, essential dimension or parameter that characterizes another entity.
-
D.
hasKeyStructure
Indicates that one entity possesses or defines the primary structural framework or core structural pattern of another entity.
-
E.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:33 p.m.