Triple
T6902612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aceh Sultanate |
E159529
|
entity |
| Predicate | emergedAsMajorPowerInCentury |
P56906
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Aceh Sultanate, emergedAsMajorPowerInCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergedAsMajorPowerInCentury Context triple: [Aceh Sultanate, emergedAsMajorPowerInCentury, 16th century]
-
A.
cameToPowerInCentury
Indicates that an entity assumed ruling authority or control during a specified century.
-
B.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
C.
historicalEraOfRise
Indicates the historical era or period during which an entity first rose to prominence, influence, or significance.
-
D.
historicalPeriodOfExpansion
Indicates a historical period during which the referenced entity underwent significant growth, enlargement, or territorial/organizational expansion.
-
E.
centuryOfGreatestInfluence
chosen
Indicates the century during which an entity exerted its greatest impact or influence.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d988a5b48190a9238047e86f314c |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.