Triple
T24544430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sa'i |
E607181
|
entity |
| Predicate | involvesWalkingBetween |
P90518
|
FINISHED |
| Object | Safa |
—
|
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: Safa | Statement: [Sa'i, involvesWalkingBetween, Safa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesWalkingBetween Context triple: [Sa'i, involvesWalkingBetween, Safa]
-
A.
walkThrough
Indicates moving through or along the interior or extent of something, typically traversing a space or environment from one side or point to another.
-
B.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
C.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
D.
hasWalkingRouteConnection
chosen
Indicates that there is a walkable path or route directly connecting two locations.
-
E.
walks
Indicates that an entity moves on foot from one place to another, typically at a regular, moderate pace.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:26 a.m.