Triple
T23874733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Shahania SC |
E592832
|
entity |
| Predicate | hasDomesticManagers |
P154279
|
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: [Al-Shahania SC, hasDomesticManagers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomesticManagers Context triple: [Al-Shahania SC, hasDomesticManagers, true]
-
A.
basedInAsManager
Indicates that an entity serves in the role of manager at, or is professionally based as a manager in, a particular organization or location.
-
B.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
C.
activeAsManager
Indicates that an entity currently holds and performs the role or responsibilities of a manager in relation to another entity.
-
D.
hasEmployees
Indicates that one entity employs one or more other entities as its workers or staff.
-
E.
hasEstateManager
Indicates that an entity is responsible for managing, overseeing, or administering the estate or property of another entity.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cc00420c8190b841ea15044961d8 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:15 p.m.