Triple
T1722076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trilateral Commission |
E37413
|
entity |
| Predicate | sectorRepresented |
P31178
|
FINISHED |
| Object | political leaders |
—
|
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: political leaders | Statement: [Trilateral Commission, sectorRepresented, political leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorRepresented Context triple: [Trilateral Commission, sectorRepresented, political leaders]
-
A.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
B.
memberRepresents
Indicates that one entity serves as an official representative or delegate acting on behalf of another entity within a group, organization, or body.
-
C.
eraRepresented
Indicates that a subject depicts, symbolizes, or stands for a particular historical or temporal era.
-
D.
partyRepresentation
Indicates that one party acts on behalf of, or serves as the representative of, another party in a given context or proceeding.
-
E.
cityRepresented
Indicates that one entity serves as the official representative or governing body for a particular city.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aadb68868c819097ec6db6194abae6 |
completed | March 6, 2026, 1:49 p.m. |
Created at: March 4, 2026, 7:30 p.m.