Triple
T9651118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Valencia |
E233334
|
entity |
| Predicate | titleCreatedAsResultOf |
P33656
|
FINISHED |
| Object | conquest of Valencia |
—
|
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: conquest of Valencia | Statement: [King of Valencia, titleCreatedAsResultOf, conquest of Valencia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCreatedAsResultOf Context triple: [King of Valencia, titleCreatedAsResultOf, conquest of Valencia]
-
A.
titleCreatedFrom
Indicates that a title is derived or generated from another source, such as an existing entity, text, or identifier.
-
B.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of another entity.
-
C.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
D.
officeCreatedAsResultOf
chosen
Indicates that an office came into existence as a consequence of a specific preceding event, action, or process.
-
E.
titleCreation
Indicates that an entity is responsible for creating, originating, or authoring the title associated with another 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9baf9a1c819098c407ea7d42e6d1 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.