Triple
T11409178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everest |
E270321
|
entity |
| Predicate | pairedCoreType |
P18973
|
FINISHED |
| Object | high-efficiency core |
—
|
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: high-efficiency core | Statement: [Everest, pairedCoreType, high-efficiency core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedCoreType Context triple: [Everest, pairedCoreType, high-efficiency core]
-
A.
pairedSingleWith
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
-
B.
typicalCoreType
chosen
Indicates that something is a standard or characteristic core type within a given classification or system.
-
C.
pairedWithFunctionally
Indicates that one entity is functionally matched or coupled with another to perform a complementary or corresponding role.
-
D.
pairedMonitorType
Indicates that one monitor is associated with or linked to another monitor of a specified type as its pair.
-
E.
possibleCoregentWith
Indicates that two individuals could have ruled simultaneously as co-regents or shared sovereign authority during an overlapping period.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014e72748190a01bde2f0105cedb |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.