Triple
T5237676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tablelands |
E118262
|
entity |
| Predicate | areFoundOn |
P33560
|
FINISHED |
| Object | all continents |
—
|
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: all continents | Statement: [tablelands, areFoundOn, all continents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areFoundOn Context triple: [tablelands, areFoundOn, all continents]
-
A.
commonlyFoundOn
chosen
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
B.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
C.
livesOn
Indicates that one entity resides or has its home on or atop another entity (such as a surface, structure, or geographic feature).
-
D.
foundInRegion
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
E.
founds
Indicates that an entity establishes or creates an organization, institution, settlement, or similar entity, typically as its originator.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b27990c8190b6a3c24de09c8c18 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.