Triple
T2331423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajdabiya |
E44209
|
entity |
| Predicate | hasStrategicFunction |
P38985
|
FINISHED |
| Object | gateway to eastern Libya |
—
|
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: gateway to eastern Libya | Statement: [Ajdabiya, hasStrategicFunction, gateway to eastern Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrategicFunction Context triple: [Ajdabiya, hasStrategicFunction, gateway to eastern Libya]
-
A.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
B.
hasElectoralStrategy
Indicates that an entity employs or is associated with a specific plan or approach for winning or influencing an election.
-
C.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
D.
hasCommitteeFunction
Indicates that a committee is assigned or performs a specific function, role, or responsibility.
-
E.
hasCivicFunction
Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcc2fa25c8190858c1c541b914f4c |
completed | March 7, 2026, 6:56 a.m. |
Created at: March 4, 2026, 7:51 p.m.