Triple
T6527709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces Inaugural Committee |
E151347
|
entity |
| Predicate | activatedFor |
P71428
|
FINISHED |
| Object | each U.S. presidential inauguration |
—
|
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: each U.S. presidential inauguration | Statement: [Armed Forces Inaugural Committee, activatedFor, each U.S. presidential inauguration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activatedFor Context triple: [Armed Forces Inaugural Committee, activatedFor, each U.S. presidential inauguration]
-
A.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
B.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
C.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
D.
isActive
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
E.
activationType
Indicates the specific manner or mechanism by which an activation or triggering event occurs between entities.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ada9c8408190b1bc327985366be9 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:45 p.m.