Triple
T28135614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Legacy |
E714193
|
entity |
| Predicate | isPoliticallyEngaged |
P124343
|
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: [The Legacy, isPoliticallyEngaged, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPoliticallyEngaged Context triple: [The Legacy, isPoliticallyEngaged, true]
-
A.
reflectsPoliticalEngagement
chosen
Indicates that one entity’s behavior, expression, or state demonstrates or reveals its level or nature of involvement in political processes or activities.
-
B.
participatesInPoliticsOf
Indicates involvement or active engagement by one entity in the political processes, affairs, or governance activities of another entity.
-
C.
politicalActivityLevel
Indicates the degree or intensity of an entity’s involvement or participation in political actions, events, or processes.
-
D.
hasPoliticalActivityIn
Indicates that an entity engages in or is associated with political activities within a specified location or jurisdiction.
-
E.
electoralActivityLevel
Indicates the degree or intensity of participation or engagement in electoral processes or activities.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6412eece8819083585f8d75aff17d |
completed | May 2, 2026, 6:23 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:49 p.m.