Triple
T2720182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracy Pumping Plant |
E60062
|
entity |
| Predicate | inServiceSince |
P2451
|
FINISHED |
| Object | early 1950s |
—
|
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: early 1950s | Statement: [Tracy Pumping Plant, inServiceSince, early 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inServiceSince Context triple: [Tracy Pumping Plant, inServiceSince, early 1950s]
-
A.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
-
B.
inUseSince
chosen
Indicates that an entity has been actively in use starting from a specified point in time.
-
C.
yearOfUse
Indicates the specific year during which something was in use or actively utilized.
-
D.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
E.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdab06d388190acf690787fe58ab5 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.