Triple
T22263528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Picacho Wilderness |
E550289
|
entity |
| Predicate | mechanizedTransport |
P85612
|
FINISHED |
| Object | prohibited |
—
|
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: prohibited | Statement: [Little Picacho Wilderness, mechanizedTransport, prohibited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanizedTransport Context triple: [Little Picacho Wilderness, mechanizedTransport, prohibited]
-
A.
mechanicalTransport
chosen
Indicates a relationship where an entity is moved or carried from one place to another using a mechanical means of transportation (e.g., vehicles, machines, or devices).
-
B.
cargoVehicle
Indicates a relationship where a vehicle is used or designated for transporting cargo or goods.
-
C.
transportUnit
Indicates a relationship where one entity serves as a means or unit for transporting another entity from one place to another.
-
D.
transportTechnology
Indicates a relationship where one entity serves as the means, system, or method used to transport or move another entity from one place to another.
-
E.
transports
Indicates that one entity carries or conveys another entity from one place to another.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141b94a688190b17c55477993a745 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.