Triple
T37661520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End Midlands |
E937726
|
entity |
| Predicate | sharesMobCapWith |
P202821
|
FINISHED |
| Object | other End biomes |
—
|
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: other End biomes | Statement: [End Midlands, sharesMobCapWith, other End biomes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesMobCapWith Context triple: [End Midlands, sharesMobCapWith, other End biomes]
-
A.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
B.
sharesBayWith
Indicates that two locations are situated along or adjacent to the same bay.
-
C.
shareWith
Indicates that something is given, disclosed, or made accessible by one entity to another entity.
-
D.
sharesPlatformWith
Indicates that two entities operate on, are available through, or participate within the same platform or system.
-
E.
sharesMount
Indicates that two or more entities are attached to, use, or are positioned on the same mounting structure or support.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00bf5990e08190a8b633e237656564 |
completed | May 10, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_6a00beef4f5881909b00ac89e6af5902 |
completed | May 10, 2026, 5:22 p.m. |
| PDg | Predicate description generation | batch_6a00bf5899b08190ad012a0879907d65 |
completed | May 10, 2026, 5:24 p.m. |
Created at: May 3, 2026, 4:18 p.m.