Triple
T37903851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Greenland |
E945492
|
entity |
| Predicate | hasRulingCrown |
P189942
|
FINISHED |
| Object | Spanish Crown |
—
|
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: Spanish Crown | Statement: [Spanish Greenland, hasRulingCrown, Spanish Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulingCrown Context triple: [Spanish Greenland, hasRulingCrown, Spanish Crown]
-
A.
crownCoRuler
Indicates a relationship where two or more individuals are jointly crowned and officially recognized as co-rulers of the same realm or title.
-
B.
hasRedCrown
Indicates that the subject possesses or is characterized by a red-colored crown.
-
C.
hasCrowningJewel
Indicates that one entity possesses or is characterized by a most important, standout, or premier element represented by another entity.
-
D.
hasCrownName
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
-
E.
hasCrownCount
Indicates the number of crowns that an entity possesses or is associated with.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.