Triple
T29749829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FÉLIN soldier system |
E752862
|
entity |
| Predicate | introducedForTesting |
P23056
|
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: [FÉLIN soldier system, introducedForTesting, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedForTesting Context triple: [FÉLIN soldier system, introducedForTesting, early 2000s]
-
A.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
B.
introducedForServiceWith
Indicates that one entity was presented or brought to the attention of another entity specifically for the purpose of providing a service.
-
C.
introducedForState
Indicates that something was created, proposed, or brought forward specifically for use in or application to a particular state.
-
D.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
E.
isUsedToTest
chosen
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 28, 2026, 7:53 p.m.