Triple
T35174533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raginmund |
E1015656
|
entity |
| Predicate | hasTransformedForm |
P89273
|
FINISHED |
| Object | Ramon |
—
|
NE NERFINISHED |
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: Ramon | Statement: [Raginmund, hasTransformedForm, Ramon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransformedForm Context triple: [Raginmund, hasTransformedForm, Ramon]
-
A.
hasTransformation
chosen
Indicates that one entity changes or is converted into another entity, capturing a transformation process or result.
-
B.
hasTransformationFormula
Indicates that there exists a specific formula or rule that defines how one entity is transformed into another.
-
C.
hasReformedForm
Indicates that an entity has a later, modified, or updated form that results from a process of reform or restructuring.
-
D.
hasTransformationType
Indicates that an entity undergoes or is associated with a specific kind or category of transformation.
-
E.
hasFormed
Indicates that an entity has come together or been created into a particular structure, group, or configuration.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: May 3, 2026, 4:02 p.m.