Triple
T37032163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-10 |
E916524
|
entity |
| Predicate | hasLinePrefix |
P66954
|
FINISHED |
| Object | A |
—
|
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: A | Statement: [A-10, hasLinePrefix, A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinePrefix Context triple: [A-10, hasLinePrefix, A]
-
A.
hasLineCharacter
Indicates that one entity possesses or includes a specific character or symbol that appears within a line of text or sequence.
-
B.
hasLines
Indicates that one entity contains, is composed of, or is associated with one or more linear elements or line segments.
-
C.
hasPrefix
chosen
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
D.
hasLineNumber
Indicates that something is associated with a specific line number, typically denoting its position within an ordered sequence such as lines of text or code.
-
E.
hasLineStructure
Indicates that one entity possesses or exhibits a linear arrangement or organization of its components.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 3, 2026, 4:14 p.m.