Triple
T18965382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skull Tower |
E464020
|
entity |
| Predicate | currentNumberOfSkulls |
P110023
|
FINISHED |
| Object | around 50 |
—
|
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: around 50 | Statement: [Skull Tower, currentNumberOfSkulls, around 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentNumberOfSkulls Context triple: [Skull Tower, currentNumberOfSkulls, around 50]
-
A.
estimatedNumberOfSkulls
chosen
Indicates the approximate count of skulls associated with an entity, based on estimation rather than an exact measurement.
-
B.
hasSkull
Indicates that an entity possesses or is characterized by the presence of a skull.
-
C.
skullUsage
Indicates how a skull is used, applied, or functionally involved in a particular context or activity.
-
D.
numberOfColossalHeads
Indicates the quantity of colossal heads associated with or attributed to a given subject.
-
E.
hasSkullDisplayedSeparately
Indicates that the skull of an individual or specimen is displayed separately from the rest of its remains or body.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d663948190b496fbd2e69c7f43 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon