Triple
T28329646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lekhwya SC |
E717503
|
entity |
| Predicate | attractedHighProfileManagers |
P164681
|
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: [Lekhwya SC, attractedHighProfileManagers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attractedHighProfileManagers Context triple: [Lekhwya SC, attractedHighProfileManagers, true]
-
A.
hasInternationalManagers
Indicates that an entity has managers who operate or are responsible for activities in multiple countries or international contexts.
-
B.
activeAsManager
Indicates that an entity currently holds and performs the role or responsibilities of a manager in relation to another entity.
-
C.
hasDomesticManagers
Indicates that an entity has managers responsible for overseeing its operations within its own country or domestic context.
-
D.
wonAsManager
Indicates that one entity achieved a victory or title while serving in the role of manager of the other entity.
-
E.
notablePlayerManaged
Indicates that a notable or prominent player was managed or coached by a particular manager or team.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 12:31 a.m.