Triple
T35619237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth |
E1029263
|
entity |
| Predicate | notableFactionActivity |
P129177
|
FINISHED |
| Object | Institute operations |
—
|
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: Institute operations | Statement: [Commonwealth, notableFactionActivity, Institute operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFactionActivity Context triple: [Commonwealth, notableFactionActivity, Institute operations]
-
A.
notableActionAt
Indicates that an entity performed or was involved in a significant action or event at a specific location or point in time.
-
B.
notableActivityIn
chosen
Indicates that an entity is particularly recognized for performing a significant activity within a specified place, context, or domain.
-
C.
notableBuildingActivity
Indicates that an entity is significantly involved in a noteworthy construction, renovation, or development activity related to a building or structure.
-
D.
notableForce
Indicates that an entity is recognized as a significant or influential force affecting another entity, system, or context.
-
E.
bearerNotableEvent
Indicates that a bearer (such as a person or entity) is associated with a specific notable event in which they played a significant role.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.