Triple
T26468671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Vleck paramagnetism |
E665838
|
entity |
| Predicate | frameworkDevelopedBy |
P160780
|
FINISHED |
| Object | John Hasbrouck Van Vleck |
—
|
NE NERFINISHED |
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: John Hasbrouck Van Vleck | Statement: [Van Vleck paramagnetism, frameworkDevelopedBy, John Hasbrouck Van Vleck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameworkDevelopedBy Context triple: [Van Vleck paramagnetism, frameworkDevelopedBy, John Hasbrouck Van Vleck]
-
A.
frameworkName
Indicates that a specific framework is identified by the given name.
-
B.
developedWith
Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
-
C.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
-
D.
developedOn
Indicates that something was created, built, or produced using a particular platform, technology, or environment.
-
E.
scriptDevelopedFor
Indicates that a script was specifically created or developed for use by, or in the context of, a particular entity or purpose.
- F. None of above. chosen
Provenance (4 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612c5f208819096a791c6a90dc571 |
completed | May 2, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 27, 2026, 12:17 a.m.