Triple
T26255095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farey sequence |
E656694
|
entity |
| Predicate | includesEndpoint |
P160988
|
FINISHED |
| Object | 0/1 |
—
|
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: 0/1 | Statement: [Farey sequence, includesEndpoint, 0/1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEndpoint Context triple: [Farey sequence, includesEndpoint, 0/1]
-
A.
endpointInclusion
chosen
Indicates that one endpoint is contained within or is part of another endpoint or endpoint set.
-
B.
includesRight
Indicates that one entity contains, encompasses, or grants a particular right to another entity.
-
C.
includesPort
Indicates that one entity contains, encompasses, or has as part of it a specific port or set of ports.
-
D.
includesFinal
Indicates that one entity contains or encompasses another entity as its concluding or last part.
-
E.
includesAPI
Indicates that one entity provides or contains an application programming interface (API) that can be used by another entity.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 26, 2026, 9:08 p.m.