Triple
T19918610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Wetlands |
E478729
|
entity |
| Predicate | habitatTypeRecreated |
P22357
|
FINISHED |
| Object | marsh |
—
|
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: marsh | Statement: [Texas Wetlands, habitatTypeRecreated, marsh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: habitatTypeRecreated Context triple: [Texas Wetlands, habitatTypeRecreated, marsh]
-
A.
ecosystemReconstruction
Indicates the process of restoring or recreating an ecosystem’s structure, function, and components, often after disturbance or degradation.
-
B.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
C.
featuresHabitat
chosen
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
D.
reintroducedSpecies
Indicates that a species has been brought back and established again in an area where it had previously disappeared or been extirpated.
-
E.
formerHabitat
Indicates that a location once served as a habitat for an entity but no longer does.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c3d990819089386d9f30323e8c |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.