Triple
T37253023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-35 National Highway |
E924043
|
entity |
| Predicate | terminusLocationSouth |
P149030
|
FINISHED |
| Object | Hasan Abdal |
—
|
NE NERFINISHED |
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: Hasan Abdal | Statement: [N-35 National Highway, terminusLocationSouth, Hasan Abdal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusLocationSouth Context triple: [N-35 National Highway, terminusLocationSouth, Hasan Abdal]
-
A.
terminusSouthNear
Indicates that the southern end or terminus of one entity is located close to another entity.
-
B.
terminusCitySouth
Indicates that something serves as the southern terminus or endpoint located in a particular city.
-
C.
terminusSouthState
Indicates that the southern endpoint or terminus of an entity (such as a route or line) is located in a specified state.
-
D.
terminusSouthConnection
Indicates a connection where one entity serves as the southern terminus or endpoint of another entity.
-
E.
terminusBLocation
chosen
Indicates the location at which the B end or second endpoint of something (such as a route, connection, or segment) is situated.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:15 p.m.