Triple
T9688589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caguax |
E234478
|
entity |
| Predicate | chiefdom |
P89631
|
FINISHED |
| Object | region of present-day Caguas |
—
|
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: region of present-day Caguas | Statement: [Caguax, chiefdom, region of present-day Caguas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefdom Context triple: [Caguax, chiefdom, region of present-day Caguas]
-
A.
kingdom
Indicates that an entity is classified within a particular biological kingdom in a taxonomic hierarchy.
-
B.
chief
Indicates that one entity holds the highest-ranking leadership or authoritative position over another entity or within a specified context.
-
C.
feudalCenter
Indicates that a location serves as the primary seat of authority, administration, or power within a feudal system.
-
D.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
E.
traditionalDuchy
Indicates that an entity is recognized as a duchy according to traditional or historical territorial divisions, rather than modern administrative boundaries.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d019d40819095059a4d6167900a |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:17 p.m.