Triple
T27261622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-11 |
E687779
|
entity |
| Predicate | hasLineSymbol |
P25256
|
FINISHED |
| Object | F |
—
|
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: F | Statement: [F-11, hasLineSymbol, F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineSymbol Context triple: [F-11, hasLineSymbol, F]
-
A.
lineSymbol
chosen
Indicates that one entity is used as a line-style or line-representation symbol for another entity.
-
B.
hasLineStyle
Indicates that one entity is associated with or uses a particular style or pattern of line representation in relation to another entity.
-
C.
hasLines
Indicates that one entity contains, is composed of, or is associated with one or more linear elements or line segments.
-
D.
hasLineRole
Indicates that an entity participates in a line (such as a queue, route, or sequence) with a specific functional role or position within that line.
-
E.
hasLineCharacter
Indicates that one entity possesses or includes a specific character or symbol that appears within a line of text or sequence.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 10:53 a.m.