Triple
T20145630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-1FTB |
E491294
|
entity |
| Predicate | hasModificationPurpose |
P124103
|
FINISHED |
| Object | test instrumentation integration |
—
|
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: test instrumentation integration | Statement: [C-1FTB, hasModificationPurpose, test instrumentation integration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModificationPurpose Context triple: [C-1FTB, hasModificationPurpose, test instrumentation integration]
-
A.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
B.
hasReconstructionPurpose
Indicates that something exists or is performed with the specific aim or function of reconstruction (e.g., rebuilding, restoring, or re-creating something).
-
C.
showsModificationBy
Indicates that one entity displays or reveals the changes, alterations, or modifications that have been made by another entity.
-
D.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
E.
hasEstablishedPurpose
chosen
Indicates that an entity has a defined and recognized purpose or intended function already determined.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679e43a48190b3a5da5710b07ff7 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.