Triple
T36190550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Scientists |
E1046973
|
entity |
| Predicate | disciplineRepresentation |
P121458
|
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: [The Scientists, disciplineRepresentation, Physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disciplineRepresentation Context triple: [The Scientists, disciplineRepresentation, Physics]
-
A.
disciplineFormat
Indicates the specific organizational or presentation format in which a discipline or field of study is structured or expressed.
-
B.
disciplineCode
chosen
Indicates the specific field, subject area, or branch of study/classification to which an entity is assigned or categorized.
-
C.
disciplineStrength
Indicates the degree or intensity of self-control or disciplined behavior an entity exhibits in its actions or decisions.
-
D.
governingDiscipline
Indicates that one discipline or field provides the primary rules, principles, or framework that regulate or guide another activity, domain, or practice.
-
E.
disciplineCombination
Indicates a relationship where multiple disciplines are combined or integrated into a unified or joint context.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.