Triple
T22197231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XPath 3.1 |
E548578
|
entity |
| Predicate | hasLiteralSyntax |
P95858
|
FINISHED |
| Object | map literal |
—
|
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: map literal | Statement: [XPath 3.1, hasLiteralSyntax, map literal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiteralSyntax Context triple: [XPath 3.1, hasLiteralSyntax, map literal]
-
A.
hasLiteralReferent
Indicates that a linguistic expression directly refers to a specific, concrete entity or value rather than to an abstract or interpreted meaning.
-
B.
hasLiteralMeaning
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
-
C.
hasSyntaxKeyword
chosen
Indicates that an element or construct is associated with, or marked by, a specific keyword in the syntax of a language or formal system.
-
D.
hasLiteralProtocol
Indicates that an entity is associated with a specific, explicitly defined communication or data-handling protocol.
-
E.
hasExpression
Indicates that an entity displays or possesses a particular facial or emotional expression.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae7c72081909b7817d66391bef4 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.