Triple
T31943842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_ts |
E815593
|
entity |
| Predicate | hasRowIndex |
P128513
|
FINISHED |
| Object | t |
—
|
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: t | Statement: [V_ts, hasRowIndex, t]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRowIndex Context triple: [V_ts, hasRowIndex, t]
-
A.
hasRow
Indicates that one entity contains, includes, or is associated with a specific row within a structured arrangement such as a table, grid, or dataset.
-
B.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
C.
hasIndexes
Indicates that an entity possesses one or more index structures or references used for organizing, locating, or accessing its associated data or elements.
-
D.
rowIndexing
chosen
Indicates that one entity selects or refers to specific rows or row positions within another entity, typically in a tabular or matrix-like structure.
-
E.
hasIndexSet
Indicates that something is associated with, defined over, or organized according to a particular set of indices.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 1, 2026, 12:06 a.m.