Triple
T26402130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pero da Covilhã |
E663728
|
entity |
| Predicate | notableJourneyType |
P197789
|
FINISHED |
| Object | overland journey |
—
|
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: overland journey | Statement: [Pero da Covilhã, notableJourneyType, overland journey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableJourneyType Context triple: [Pero da Covilhã, notableJourneyType, overland journey]
-
A.
notableDestinationType
Indicates the general category or type of destination for which something is considered notable.
-
B.
notableRouteType
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
-
C.
notableDestination
Indicates that a location is recognized as a significant or prominent place that people commonly travel to or aim to visit.
-
D.
notableTour
Indicates that an entity is recognized for having a significant or well-known tour associated with it.
-
E.
notableVisit
Indicates that one entity made a visit to another entity or location that is considered significant or noteworthy.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
| PDg | Predicate description generation | batch_69feabcca6148190a8eb7b6fa33729c7 |
completed | May 9, 2026, 3:36 a.m. |
Created at: April 26, 2026, 11:32 p.m.