Triple
T700016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelantado of Florida |
E13977
|
entity |
| Predicate | conferringAuthority |
P14126
|
FINISHED |
| Object | conquer Florida |
—
|
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: conquer Florida | Statement: [Adelantado of Florida, conferringAuthority, conquer Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferringAuthority Context triple: [Adelantado of Florida, conferringAuthority, conquer Florida]
-
A.
designationAuthority
chosen
Indicates the entity that has the official power or responsibility to assign, grant, or confer a particular designation to another entity.
-
B.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
C.
legalAuthorityOver
Indicates that one entity has the recognized power or right to make, enforce, or adjudicate rules or decisions concerning another entity.
-
D.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
E.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a544e3608190ac315c7aa9f88e7e |
completed | March 1, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ec8c748190b198492a0eea4445 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.