Triple
T9637432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born–Infeld electrodynamics |
E232968
|
entity |
| Predicate | hasEquationType |
P16808
|
FINISHED |
| Object | nonlinear field equations |
—
|
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: nonlinear field equations | Statement: [Born–Infeld electrodynamics, hasEquationType, nonlinear field equations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEquationType Context triple: [Born–Infeld electrodynamics, hasEquationType, nonlinear field equations]
-
A.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
C.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
D.
hasStandardType
Indicates that something conforms to or is categorized under a defined standard classification or type.
-
E.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b5045cc8190ab717f42d803e010 |
completed | April 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.