Triple
T23641204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madoc ab Owain Gwynedd |
E583898
|
entity |
| Predicate | allegedCompanions |
P153002
|
FINISHED |
| Object | group of Welsh settlers |
—
|
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: group of Welsh settlers | Statement: [Madoc ab Owain Gwynedd, allegedCompanions, group of Welsh settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedCompanions Context triple: [Madoc ab Owain Gwynedd, allegedCompanions, group of Welsh settlers]
-
A.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
B.
hasNumberOfCompanions
Indicates the quantity of companions or associates that an entity has.
-
C.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
D.
allegedAgentOf
Indicates that one entity is claimed or suspected, but not confirmed, to be the agent responsible for an action or event involving another entity.
-
E.
associatedBeings
Indicates that two or more beings are linked or connected to each other in some relevant way.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b28152108190972ac680cba986d7 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:48 p.m.