Triple
T32879367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayer f-function formalism |
E841012
|
entity |
| Predicate | representsBondsAs |
P72867
|
FINISHED |
| Object | Mayer f-functions |
—
|
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: Mayer f-functions | Statement: [Mayer f-function formalism, representsBondsAs, Mayer f-functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsBondsAs Context triple: [Mayer f-function formalism, representsBondsAs, Mayer f-functions]
-
A.
bondsFormed
Indicates that a connection or attachment has been created between two or more entities.
-
B.
doubleBonds
Indicates that there are two shared pairs of electrons (a double covalent bond) between the related entities.
-
C.
hasBondType
Indicates the specific kind of bond or connection that exists between two related entities.
-
D.
representsAs
chosen
Indicates that one entity serves as a depiction, symbol, or stand-in for another entity in some representational context.
-
E.
involvesForceBond
Indicates a relationship in which two or more entities are connected through a special Force-based bond that links their sensations, emotions, or abilities.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 1, 2026, 1:18 a.m.