Triple
T25343509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pheasant Island |
E635478
|
entity |
| Predicate | hasCondominiumPartners |
P181104
|
FINISHED |
| Object | French Republic |
—
|
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: French Republic | Statement: [Pheasant Island, hasCondominiumPartners, French Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCondominiumPartners Context triple: [Pheasant Island, hasCondominiumPartners, French Republic]
-
A.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
B.
hasMunicipalPartnershipWith
Indicates a formal cooperative or collaborative relationship established between two municipalities, typically involving shared projects, services, or governance initiatives.
-
C.
hasExPartner
Indicates that one entity was formerly in a romantic or intimate partnership with another entity, but that relationship has ended.
-
D.
hasPartnershipType
Indicates the specific kind or category of partnership relationship that exists between entities.
-
E.
hasPartnerOrganization
Indicates that an entity is formally associated or collaborates with another entity as a partner organization.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 21, 2026, 1:32 p.m.