Triple
T17713191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAR2 |
E441620
|
entity |
| Predicate | hasKeyAdvantage |
P7339
|
FINISHED |
| Object | very high neutron flux at sample position |
—
|
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: very high neutron flux at sample position | Statement: [EAR2, hasKeyAdvantage, very high neutron flux at sample position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyAdvantage Context triple: [EAR2, hasKeyAdvantage, very high neutron flux at sample position]
-
A.
hasAdvantage
Indicates that one entity possesses a benefit, edge, or favorable position over another in a given context.
-
B.
hasBraggingRightsOver
Indicates that one entity can legitimately claim superiority or achievement over another, often as a basis for boasting.
-
C.
notableAdvantage
chosen
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
-
D.
hasKeyClub
Indicates that an entity is associated with or belongs to a Key Club organization or group.
-
E.
hasKeyBattle
Indicates that an entity is associated with a major or decisive battle that is central to its history, role, or significance.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729cebd08190872be96a26d0f7ce |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.