Triple
T461574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | equivalence principle |
E7349
|
entity |
| Predicate | experimentalStatus |
P127
|
FINISHED |
| Object | verified to very high precision |
—
|
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: verified to very high precision | Statement: [equivalence principle, experimentalStatus, verified to very high precision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experimentalStatus Context triple: [equivalence principle, experimentalStatus, verified to very high precision]
-
A.
testStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, or is still in progress.
-
B.
hasTypeOfExperiment
Indicates that an experiment is associated with or classified under a specific type or category of experiment.
-
C.
hostsExperiment
Indicates that one entity provides the environment or infrastructure in which another entity’s experiment is conducted or run.
-
D.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
E.
status
chosen
Indicates the current condition, state, or standing of an entity within a given 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efbed5b88190a45716812eb4cfdf |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.