Triple
T31943824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_ts |
E815593
|
entity |
| Predicate | elementOfRow |
P25794
|
FINISHED |
| Object | V_td V_ts V_tb |
—
|
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: V_td V_ts V_tb | Statement: [V_ts, elementOfRow, V_td V_ts V_tb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elementOfRow Context triple: [V_ts, elementOfRow, V_td V_ts V_tb]
-
A.
hasRow
chosen
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.
columnIn
Indicates that one entity is located within or belongs to a specific column of another structured entity (such as a table or grid).
-
C.
rowIndexing
Indicates that one entity selects or refers to specific rows or row positions within another entity, typically in a tabular or matrix-like structure.
-
D.
rowInAssociation
Indicates that one entity functions as a specific row or record within an association or associative structure involving another entity.
-
E.
rowAlignment
Indicates that multiple items are arranged in a row with a specified horizontal alignment relative to each other or to a reference.
- 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_69f6b2758cec8190b0521eb7f2eccb42 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:06 a.m.