Triple
T14835110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Porto Praya |
E348810
|
entity |
| Predicate | tookPlaceInNeutralPort |
P17812
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Battle of Porto Praya, tookPlaceInNeutralPort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceInNeutralPort Context triple: [Battle of Porto Praya, tookPlaceInNeutralPort, true]
-
A.
usesNeutralVenueForFinal
Indicates that the final match or event in a competition is held at a neutral venue, not the home ground of either participating side.
-
B.
positionOnNeutrality
Indicates the stance or viewpoint an entity holds regarding neutrality in a given context (e.g., political, ethical, or diplomatic).
-
C.
isNeutralSite
chosen
Indicates that a location serves as an impartial or non-aligned site for an interaction, event, or relationship between parties.
-
D.
involvedNeutralShips
Indicates that neutral ships are involved or participate in a particular event, situation, or interaction.
-
E.
isNeutralOn
Indicates a stance of neither support nor opposition toward a subject, remaining impartial or undecided.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded076ac9c8190a05cabec5e87d207 |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:52 a.m.