Triple
T26650263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedra Branca |
E669028
|
entity |
| Predicate | historicalAdminBy |
P10783
|
FINISHED |
| Object | British Straits Settlements |
—
|
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: British Straits Settlements | Statement: [Pedra Branca, historicalAdminBy, British Straits Settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalAdminBy Context triple: [Pedra Branca, historicalAdminBy, British Straits Settlements]
-
A.
administrativeHistory
Indicates the sequence of past administrative changes, statuses, or governing arrangements that have affected an entity over time.
-
B.
historicallyControlledBy
Indicates that an entity was under the control, rule, or governance of another entity during some period in the past.
-
C.
formerAdministeredBy
chosen
Indicates that an entity was previously administered or managed by another entity, but is no longer under that administration.
-
D.
historicalHeir
Indicates that one entity is recognized as the successor or inheritor of another in a historical or dynastic context.
-
E.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 27, 2026, 2:32 a.m.