Triple
T23901661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Juby |
E601060
|
entity |
| Predicate | presentDayMainTown |
P138593
|
FINISHED |
| Object | Tarfaya |
—
|
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: Tarfaya | Statement: [Cape Juby, presentDayMainTown, Tarfaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayMainTown Context triple: [Cape Juby, presentDayMainTown, Tarfaya]
-
A.
presentDayTownName
Indicates that the object is the current or modern-day town name corresponding to the subject.
-
B.
presentDayMunicipality
Indicates that one entity is the current-day municipality encompassing or corresponding to the area or jurisdiction of another (typically historical) entity.
-
C.
presentDayCityIs
chosen
Indicates that one entity is the current, modern-day city corresponding to or located at the place represented by the other entity.
-
D.
presentDayCenter
Indicates that an entity currently serves as the central or primary focal point (e.g., administrative, cultural, or functional center) of another entity in the present day.
-
E.
presentDayDistrict
Indicates that one administrative district corresponds to or is located within the boundaries of a specified present-day district.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdde91d081908df44442a20e0fd2 |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.