Triple
T1842000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAMAS assault rifle |
E41196
|
entity |
| Predicate | inServiceFrom |
P34033
|
FINISHED |
| Object | 1978 |
—
|
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: 1978 | Statement: [FAMAS assault rifle, inServiceFrom, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inServiceFrom Context triple: [FAMAS assault rifle, inServiceFrom, 1978]
-
A.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
B.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
C.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
D.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:33 p.m.