Triple
T6991554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTF-8 |
E162096
|
entity |
| Predicate | usesPrefixEncoding |
P66290
|
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: [UTF-8, usesPrefixEncoding, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPrefixEncoding Context triple: [UTF-8, usesPrefixEncoding, true]
-
A.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
B.
namespacePrefix
chosen
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
-
C.
hasOriginalPrefix
Indicates that an entity retains or is associated with its initial or primary prefix from which later forms or variants are derived.
-
D.
standardPrefix
Indicates that one entity serves as the conventional or officially recognized prefix used before another entity.
-
E.
usesCodec
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc1f63c8190837cfd71cf5ed613 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.