Triple
T7150566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartree–Fock method |
E166679
|
entity |
| Predicate | usedAsReferenceFor |
P39729
|
FINISHED |
| Object | post-Hartree–Fock methods |
—
|
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: post-Hartree–Fock methods | Statement: [Hartree–Fock method, usedAsReferenceFor, post-Hartree–Fock methods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsReferenceFor Context triple: [Hartree–Fock method, usedAsReferenceFor, post-Hartree–Fock methods]
-
A.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
B.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
C.
usedAsSourceIn
chosen
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
-
D.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
E.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f28b188190b1732ca711666531 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.