Triple
T5237703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tablelands |
E118262
|
entity |
| Predicate | mayBeDescribedAs |
P21265
|
FINISHED |
| Object | upland plains |
—
|
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: upland plains | Statement: [tablelands, mayBeDescribedAs, upland plains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDescribedAs Context triple: [tablelands, mayBeDescribedAs, upland plains]
-
A.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
hasDescription
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
C.
laterDescribedAs
Indicates that an entity is referred to or characterized by a particular description or label at a later time.
-
D.
mayBeSubjectOf
Indicates that an entity has the potential or possibility to serve as the subject in a given relation, event, or statement.
-
E.
isFrequentlyDescribedAs
chosen
Indicates that something is often characterized or referred to using a particular description or set of attributes.
- 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.