Triple
T15967084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legia Warsaw |
E387218
|
entity |
| Predicate | hasUltras |
P120642
|
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: [Legia Warsaw, hasUltras, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUltras Context triple: [Legia Warsaw, hasUltras, yes]
-
A.
isUltra
Indicates that an entity possesses an extreme, superior, or beyond-standard degree of a particular quality, status, or capability.
-
B.
hasMP
Indicates that an entity is represented by, or associated with, a specific Member of Parliament (MP).
-
C.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
D.
hasSept
Indicates that one entity possesses, contains, or is associated with a sept (a subdivision or clan group) in relation to another entity.
-
E.
hasSuperpower
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:54 a.m.