Triple
T31569440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Close to Critical |
E805511
|
entity |
| Predicate | hasScienceDiscipline |
P83017
|
FINISHED |
| Object | physics |
—
|
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: physics | Statement: [Close to Critical, hasScienceDiscipline, physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScienceDiscipline Context triple: [Close to Critical, hasScienceDiscipline, physics]
-
A.
hasScience
chosen
Indicates that an entity possesses, includes, or is associated with a particular scientific discipline, content, or attribute.
-
B.
studiedByDiscipline
Indicates that a subject (such as a phenomenon, object, or concept) is examined, analyzed, or researched within a particular academic or professional discipline.
-
C.
hasMathematicalDiscipline
Indicates that one entity is associated with or characterized by a particular branch or field of mathematics.
-
D.
hasScienceBody
Indicates that an entity is associated with or possesses a scientific body, such as a scientific organization, committee, or authoritative scientific group.
-
E.
studiedInSubdiscipline
Indicates that an entity pursued study or academic work within a specific subdiscipline of a broader field.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 30, 2026, 10:19 p.m.