Triple
T34481371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimaatre |
E885193
|
entity |
| Predicate | appearsOnObjectsType |
P76740
|
FINISHED |
| Object | stelae |
—
|
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: stelae | Statement: [Nimaatre, appearsOnObjectsType, stelae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsOnObjectsType Context triple: [Nimaatre, appearsOnObjectsType, stelae]
-
A.
mayAppearOn
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
-
B.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
C.
presentsObject
Indicates that one entity formally introduces, displays, or offers another entity as an object (such as an item, work, or subject) to an audience or recipient.
-
D.
appearsInVariant
Indicates that an entity is present or occurs within a particular variant or version of another entity.
-
E.
typicalObjectType
chosen
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 1, 2026, 2:01 a.m.