Triple
T18696406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telepylus harbor |
E457125
|
entity |
| Predicate | hasInhabitantsCharacteristic |
P132337
|
FINISHED |
| Object | man-eating |
—
|
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: man-eating | Statement: [Telepylus harbor, hasInhabitantsCharacteristic, man-eating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInhabitantsCharacteristic Context triple: [Telepylus harbor, hasInhabitantsCharacteristic, man-eating]
-
A.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
B.
isInhabitedRegion
Indicates that a region has living beings (such as humans or animals) residing within its boundaries.
-
C.
hasInUniverseInhabitants
Indicates that a universe or fictional setting contains certain beings or populations as its inhabitants.
-
D.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
-
E.
hasPrimaryOccupants
Indicates that certain entities are the main or principal occupants of another entity (such as a space, structure, or location).
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e8bc408190ab41b3c21003c249 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:49 a.m.