Triple
T20797838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode Standard version 6.0 |
E511957
|
entity |
| Predicate | includesBlock |
P1393
|
FINISHED |
| Object | Mandaic block |
—
|
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: Mandaic block | Statement: [Unicode Standard version 6.0, includesBlock, Mandaic block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBlock Context triple: [Unicode Standard version 6.0, includesBlock, Mandaic block]
-
A.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
includesSee
Indicates that one entity’s scope, content, or experience contains or encompasses the act of seeing or visual perception involving another entity.
-
C.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2ae2c4c819087f620df31dc1aba |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:39 p.m.