Triple
T5676586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresnel zones |
E125099
|
entity |
| Predicate | pathDifferenceBetweenAdjacentZones |
P65922
|
FINISHED |
| Object | lambda_over_2 |
—
|
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: lambda_over_2 | Statement: [Fresnel zones, pathDifferenceBetweenAdjacentZones, lambda_over_2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pathDifferenceBetweenAdjacentZones Context triple: [Fresnel zones, pathDifferenceBetweenAdjacentZones, lambda_over_2]
-
A.
pointDifference
Indicates the numerical difference in points or scores between two compared entities.
-
B.
numberOfZones
Indicates the quantity of distinct zones associated with or contained by a given entity.
-
C.
fareZoneHierarchyPosition
Indicates the relative level or rank of a fare zone within a hierarchical fare zone structure.
-
D.
railwayZoneNumber
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
-
E.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c0252e18988190a8f3aa0684c12fb8 |
completed | March 22, 2026, 5:21 p.m. |
Created at: March 22, 2026, 3:43 p.m.