Triple
T24440463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beeston Regis |
E616244
|
entity |
| Predicate | hasQualifierInName |
P13306
|
FINISHED |
| Object | Regis indicating royal association |
—
|
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: Regis indicating royal association | Statement: [Beeston Regis, hasQualifierInName, Regis indicating royal association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQualifierInName Context triple: [Beeston Regis, hasQualifierInName, Regis indicating royal association]
-
A.
hasQualifier
chosen
Indicates that one entity serves as a qualifier or modifier that further specifies or restricts the meaning or scope of another entity or statement.
-
B.
hasNameInNotation
Indicates that an entity is referred to by a specific name or label within a particular notation or symbolic system.
-
C.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
D.
hasRuleName
Indicates that an entity is associated with a specific rule identified by a particular name.
-
E.
hasNameCharacteristic
Indicates that an entity possesses a specific quality or attribute related to its name.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2978a5cac81909d2141b606714fd4 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.