Triple
T3772514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Tunis |
E83229
|
entity |
| Predicate | regionallySignificant |
P12510
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [University of Tunis, regionallySignificant, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallySignificant Context triple: [University of Tunis, regionallySignificant, yes]
-
A.
hasRegionalSignificance
chosen
Indicates that something holds particular importance, influence, or relevance within a specific geographic region.
-
B.
notableInRegion
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
C.
regionallyRecognizedAs
Indicates that an entity is acknowledged or designated under a specific name, status, or classification within a particular geographic region or locality.
-
D.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
notableRegionOfSettlement
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc3219b881908a2f82126f9a679d |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.