Triple
T19871320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frenchman Flat |
E477522
|
entity |
| Predicate | postTestingUse |
P134450
|
FINISHED |
| Object | environmental remediation studies |
—
|
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: environmental remediation studies | Statement: [Frenchman Flat, postTestingUse, environmental remediation studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postTestingUse Context triple: [Frenchman Flat, postTestingUse, environmental remediation studies]
-
A.
isUsedToTest
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
B.
postUse
chosen
Indicates that one entity is used or occurs after another entity has been used or has taken place.
-
C.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
-
D.
test
Indicates that an entity performs, undergoes, or is associated with a testing or examination process involving another entity or condition.
-
E.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658a3d2b08190ad81914d4860df0e |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.