Triple
T7552181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hieroglyphic Stairway |
E178563
|
entity |
| Predicate | numberOfGlyphBlocks |
P7832
|
FINISHED |
| Object | over 2200 |
—
|
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: over 2200 | Statement: [Hieroglyphic Stairway, numberOfGlyphBlocks, over 2200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfGlyphBlocks Context triple: [Hieroglyphic Stairway, numberOfGlyphBlocks, over 2200]
-
A.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
-
B.
hasApproximateNumberOfPictographs
Indicates that an entity is associated with a quantity of pictographs that is not exact but estimated or approximate.
-
C.
estimatedNumberOfBlocks
chosen
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
D.
numberOfSpans
Indicates the total count of distinct spans or segments associated with an entity or within a specified context.
-
E.
numberOfCurves
Indicates the relationship that specifies how many distinct curves are associated with or contained in a given entity.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8b6c6488190b8fd94aca6ea8486 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.