Triple

T11162667
Position Surface form Disambiguated ID Type / Status
Subject Cardinal Lemoine E264075 entity
Predicate locatedOnAxe P94368 FINISHED
Object east–west axis of Line 10 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: east–west axis of Line 10 | Statement: [Cardinal Lemoine, locatedOnAxe, east–west axis of Line 10]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedOnAxe
Context triple: [Cardinal Lemoine, locatedOnAxe, east–west axis of Line 10]
  • A. isOnAxis chosen
    Indicates that one entity lies directly along a specified axis or reference line defined by another entity or coordinate system.
  • B. formsAxisOf
    Indicates that one entity serves together with another as the central line or primary axis around which a structure, system, or configuration is organized.
  • C. coordinateAxis
    Indicates that one entity serves as a reference axis or directional basis for positioning, measuring, or orienting another entity in a coordinate system.
  • D. ridgeAxis
    Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
  • E. usesAxis
    Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
  • 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8832fe88190a74d81f9ed547baa completed April 9, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69d75cec26fc8190a5497d186306f935 completed April 9, 2026, 8:01 a.m.
Created at: April 8, 2026, 9:29 p.m.