Triple
T20108613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Random—Burin—St. George’s |
E490263
|
entity |
| Predicate | containsNameElement |
P37982
|
FINISHED |
| Object | Random |
—
|
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: Random | Statement: [Random—Burin—St. George’s, containsNameElement, Random]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsNameElement Context triple: [Random—Burin—St. George’s, containsNameElement, Random]
-
A.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
B.
basedOnElementName
Indicates that one entity is derived from, determined by, or otherwise depends on the name of another element.
-
C.
hasFamilyNameElement
Indicates that an entity has a specific component or segment that forms part of its family name.
-
D.
nameElementIn
chosen
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
E.
hasComponentGivenName
Indicates that an entity includes a component whose specific given (first) name is the value of the predicate.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666ddb09881909ad2aedd1e8a78da |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:28 p.m.