Triple
T4376201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secure Communities |
E99011
|
entity |
| Predicate | reactivationDate |
P28440
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Secure Communities, reactivationDate, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactivationDate Context triple: [Secure Communities, reactivationDate, 2017]
-
A.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
-
B.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
-
C.
reconstitutionDate
Indicates the date on which something (typically a substance, solution, or entity) is restored or prepared from a prior, preserved, or inactive state.
-
D.
activationTime
chosen
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
E.
automationDate
Indicates the date on which an action, process, or system becomes automated or is scheduled to be handled automatically.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3523d4e888190b4367ed6aa17d463 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.