Triple
T26776319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antillean Confederation movement |
E670128
|
entity |
| Predicate | proposedMember |
P168577
|
FINISHED |
| Object | Puerto Rico |
—
|
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: Puerto Rico | Statement: [Antillean Confederation movement, proposedMember, Puerto Rico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedMember Context triple: [Antillean Confederation movement, proposedMember, Puerto Rico]
-
A.
wereProposedBy
Indicates that one or more entities (such as ideas, plans, or items) were put forward or suggested by a specific agent or source.
-
B.
coProposedBy
Indicates that a proposal, idea, or item is jointly put forward or suggested by multiple entities together.
-
C.
committeeMember
Indicates that an entity serves as a member of a particular committee.
-
D.
recruitedMember
Indicates that one entity has actively enlisted, signed up, or brought another entity into a group, organization, or effort as a member.
-
E.
proposerRole
Indicates the role or capacity in which an entity acts as the proposer of something, such as an offer, idea, or action.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 4:05 a.m.