Triple
T7313371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenakel |
E168148
|
entity |
| Predicate | hasDemonstratives |
P64952
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lenakel, hasDemonstratives, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemonstratives Context triple: [Lenakel, hasDemonstratives, true]
-
A.
hasDemonstrativeSystem
chosen
Indicates that an entity possesses or employs a system of demonstratives (e.g., words or markers used to indicate spatial, temporal, or discourse-related reference such as “this,” “that,” “these,” “those”).
-
B.
hasDefinitenessDistinction
Indicates that a language or system grammatically distinguishes between definite and indefinite (or otherwise specified) reference in its expressions.
-
C.
hasPronounForIt
Indicates that one entity serves as the pronoun form referring to another entity.
-
D.
determinativeFor
Indicates that one entity serves to uniquely identify, specify, or determine the status, interpretation, or outcome of another entity.
-
E.
hasDemonstration
Indicates that one entity includes, is accompanied by, or is associated with a demonstration or illustrative example of another entity or concept.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ec02319c819096d25e3683943886 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.