Triple
T31728295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medrano II |
E809787
|
entity |
| Predicate | subjectForm |
P186476
|
FINISHED |
| Object | female 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: female figure | Statement: [Medrano II, subjectForm, female figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectForm Context triple: [Medrano II, subjectForm, female figure]
-
A.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
B.
inscriptionSubject
Indicates that an inscription is about, refers to, or is dedicated to a particular subject or entity.
-
C.
submissionType
Indicates the specific category or format under which something is submitted (e.g., as a document, assignment, application, or other submission class).
-
D.
subjectKey
Indicates that the subject serves as a unique key or identifier used to reference or distinguish an entity in a relationship or dataset.
-
E.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 30, 2026, 11:20 p.m.