Triple
T31697060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gevaot |
E808944
|
entity |
| Predicate | convertedToCivilianUse |
P154373
|
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: [Gevaot, convertedToCivilianUse, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToCivilianUse Context triple: [Gevaot, convertedToCivilianUse, early 2000s]
-
A.
civilianUse
Indicates that something is intended for, suitable for, or actually used by civilians rather than military or combat purposes.
-
B.
civilianVariant
Indicates that one entity is a civilian version or non-military counterpart of another entity.
-
C.
civilUseStatus
chosen
Indicates the status or condition of how something is used for civilian (non-military) purposes.
-
D.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
E.
militaryUseEnd
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 30, 2026, 11:10 p.m.