Triple
T8181374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SUBE card |
E191067
|
entity |
| Predicate | dataStored |
P1596
|
FINISHED |
| Object | card identifier |
—
|
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: card identifier | Statement: [SUBE card, dataStored, card identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataStored Context triple: [SUBE card, dataStored, card identifier]
-
A.
dataStorage
chosen
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
B.
storesDataType
Indicates that an entity is designed to hold, manage, or persist information of a specified data type.
-
C.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
D.
dataManagement
Indicates the relationship in which an entity organizes, stores, maintains, and governs data throughout its lifecycle.
-
E.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.