Triple
T1236725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bar enash |
E26564
|
entity |
| Predicate | appearsAs |
P24836
|
FINISHED |
| Object | title for a human figure |
—
|
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: title for a human figure | Statement: [bar enash, appearsAs, title for a human figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAs Context triple: [bar enash, appearsAs, title for a human figure]
-
A.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
B.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
C.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
D.
portraysActorAs
Indicates that one entity depicts or represents an actor in a particular role, character, or manner.
-
E.
announcedAs
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
- F. None of above. chosen
Provenance (4 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf17e0bc8190a066561e6b629fc0 |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb67d52c8190815d6356b79d6ed5 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:47 p.m.