Triple
T4384753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindl. |
E99214
|
entity |
| Predicate | hasFullStop |
P56281
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lindl., hasFullStop, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFullStop Context triple: [Lindl., hasFullStop, yes]
-
A.
hasStop
Indicates that something (such as a route, service, or journey) includes or is associated with a particular stop or stopping point.
-
B.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
C.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
D.
hasCapitalAtEnd
Indicates that the capital or uppercase letter appears at the end of the given string or sequence.
-
E.
hasFullForm
Indicates that one entity is the complete, expanded, or unabbreviated form of another entity.
- F. None of above. chosen
Provenance (4 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35263970c8190904ee20d81715833 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.