Triple
T26289356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern indigo snake |
E661222
|
entity |
| Predicate | homeRangeSize |
P160207
|
FINISHED |
| Object | large compared to many other snakes |
—
|
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: large compared to many other snakes | Statement: [Eastern indigo snake, homeRangeSize, large compared to many other snakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRangeSize Context triple: [Eastern indigo snake, homeRangeSize, large compared to many other snakes]
-
A.
areaProtected
Indicates that a specified geographic area is designated and managed as protected, typically restricting certain activities to conserve its natural or cultural resources.
-
B.
typicalHomeCapacity
Indicates the usual or standard number of occupants that a home is designed or expected to accommodate.
-
C.
hasAreaRange
Indicates that something’s area falls within a specified minimum-to-maximum range.
-
D.
houseDiameter
Indicates the measured diameter or widest straight-line span of a house.
-
E.
privateUseAreaRange
Indicates the range of values that the private use area (e.g., private space or area allocation) can take for the related entities.
- F. None of above. chosen
Provenance (4 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e79dbc081908c1da51cc7f79f45 |
completed | May 2, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:07 p.m.