Triple
T31015216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kfir C.10 |
E790309
|
entity |
| Predicate | enteredServiceAsUpgrade |
P178075
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Kfir C.10, enteredServiceAsUpgrade, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceAsUpgrade Context triple: [Kfir C.10, enteredServiceAsUpgrade, early 2000s]
-
A.
enteredServiceAsReplacementFor
Indicates that one entity began its period of service specifically to take over the role or function previously performed by another entity.
-
B.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
C.
enteredServiceOn
Indicates the date or time when an entity first began active use, operation, or service.
-
D.
enteredUSServiceAs
Indicates that an entity began serving in an official capacity within the United States (e.g., military, government, or public service) under a specified role or status.
-
E.
enteredServiceWithUnit
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 29, 2026, 8:57 p.m.