Triple
T11930689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BTR series armored personnel carriers |
E283900
|
entity |
| Predicate | inServiceStatus |
P7151
|
FINISHED |
| Object | many variants remain in service worldwide |
—
|
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: many variants remain in service worldwide | Statement: [BTR series armored personnel carriers, inServiceStatus, many variants remain in service worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inServiceStatus Context triple: [BTR series armored personnel carriers, inServiceStatus, many variants remain in service worldwide]
-
A.
inService
chosen
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
B.
inServiceFrom
Indicates the time or event from which an entity (such as a service, system, or asset) begins being operationally active or officially in use.
-
C.
serviceNumberStatus
Indicates the current operational or availability state associated with a specific service number.
-
D.
typicalServiceStatus
Indicates the usual or standard operational state or condition that a service is expected to be in under normal circumstances.
-
E.
serviceAvailability
Indicates whether a particular service is accessible and operational for use during a given time or under specified conditions.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90303a9a88190a4044e6310ba9b4b |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.