Triple
T17580553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monastir |
E428191
|
entity |
| Predicate | isHistoricPort |
P125751
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Monastir, isHistoricPort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricPort Context triple: [Monastir, isHistoricPort, true]
-
A.
hasHistoricPort
chosen
Indicates that an entity possesses or is associated with a port that has historical significance or longstanding historical use.
-
B.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
C.
hasPortHistory
Indicates that an entity has an associated record or log of its past port-related events, visits, or configurations.
-
D.
isInHistoricRegister
Indicates that an entity has been officially listed or recorded in a recognized historic register or registry.
-
E.
isInHistoricRegion
Indicates that an entity is located within or belongs to a historically recognized geographic region.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463cdb1608190a7e249ad6531b1dc |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.