Triple
T21021222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copperhead Strike |
E517810
|
entity |
| Predicate | hasMultipleInversions |
P22101
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Copperhead Strike, hasMultipleInversions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleInversions Context triple: [Copperhead Strike, hasMultipleInversions, true]
-
A.
hasInversionCount
Indicates that there is a specific number of pairwise order inversions present in a given sequence or arrangement.
-
B.
inversions
chosen
Indicates a relationship where the usual order, position, or hierarchy between elements is reversed or turned upside down.
-
C.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
D.
hasMultipleCreations
Indicates that an entity is associated with more than one distinct creation or produced work.
-
E.
hasMultiplePhases
Indicates that the related process, event, or activity occurs in more than one distinct phase or stage.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5db0b88190ae61ea8b38e8ecf7 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.