Triple
T25726246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABINIT |
E645121
|
entity |
| Predicate | hasPrimaryApplication |
P90081
|
FINISHED |
| Object | first-principles calculations |
—
|
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: first-principles calculations | Statement: [ABINIT, hasPrimaryApplication, first-principles calculations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryApplication Context triple: [ABINIT, hasPrimaryApplication, first-principles calculations]
-
A.
hasPrimary
chosen
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
hasPrimaryAbility
Indicates that an entity possesses a main or most important ability that characterizes its primary function or role.
-
C.
hasPrimaryActivities
Indicates that an entity is associated with one or more main activities that define its core functions or operations.
-
D.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
E.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 21, 2026, 11:04 p.m.