Triple
T36110070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Loam |
E1044468
|
entity |
| Predicate | statusOnIsland |
P200631
|
FINISHED |
| Object | socially subordinate to Crichton |
—
|
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: socially subordinate to Crichton | Statement: [Lord Loam, statusOnIsland, socially subordinate to Crichton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOnIsland Context triple: [Lord Loam, statusOnIsland, socially subordinate to Crichton]
-
A.
signedOnIsland
Indicates that the signing of an agreement, document, or contract took place on an island.
-
B.
engagedOnIsland
Indicates that two or more entities became engaged (e.g., to be married or formally committed) while they were on an island.
-
C.
hasIslandWithStatus
Indicates that an entity possesses or includes an island that has a specified status or condition.
-
D.
habitationStatusOfIsland
Indicates whether an island is inhabited, uninhabited, or otherwise characterized by a particular habitation status.
-
E.
lostIslandStatusBy
Indicates that an entity ceased to have island status as a result of an action, event, or influence attributed to another entity.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69ff9bec9d748190869caebf6bf0c78f |
completed | May 9, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:08 p.m.