Triple
T6557129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boxer Protocol |
E152476
|
entity |
| Predicate | indemnityPayableOverYears |
P71784
|
FINISHED |
| Object | 39 |
—
|
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: 39 | Statement: [Boxer Protocol, indemnityPayableOverYears, 39]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indemnityPayableOverYears Context triple: [Boxer Protocol, indemnityPayableOverYears, 39]
-
A.
policyPeriod
Indicates the time span during which a particular policy is in effect or valid.
-
B.
serviceYears
Indicates the number of years an entity has provided service or been in a particular role, position, or organization.
-
C.
requiredIndemnityReceiver
Indicates that one party is obligated to provide indemnity (compensation or protection against loss) to another specified party.
-
D.
damageYear
Indicates the year in which the damage to an entity occurred or was recorded.
-
E.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c1b007148190b5164d6d09584cdf |
completed | March 27, 2026, 5:43 p.m. |
Created at: March 27, 2026, 1:52 p.m.