Triple
T8106399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La 12 |
E189236
|
entity |
| Predicate | supporterCategory |
P13349
|
FINISHED |
| Object | organized supporters group |
—
|
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: organized supporters group | Statement: [La 12, supporterCategory, organized supporters group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supporterCategory Context triple: [La 12, supporterCategory, organized supporters group]
-
A.
supporterType
chosen
Indicates the specific role or category of support a supporter provides in relation to another entity or activity.
-
B.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
-
C.
supporter
Indicates a relationship where one entity backs, advocates for, or provides assistance to another entity, often in an ongoing or affiliative way.
-
D.
supporterIdentity
Indicates that one entity is identified as a supporter (e.g., backer, advocate, or sponsor) of another entity or cause.
-
E.
supporterStyle
Indicates the characteristic manner or approach in which a supporter provides their support.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42f735c8819090d0d822644c0a51 |
completed | March 31, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69cb04a2ed1c8190b73562321ad688bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:31 p.m.