Triple
T6902694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese conquest of Malacca |
E159530
|
entity |
| Predicate | hasPrecedent |
P3138
|
FINISHED |
| Object | Portuguese capture of Goa |
—
|
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: Portuguese capture of Goa | Statement: [Portuguese conquest of Malacca, hasPrecedent, Portuguese capture of Goa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrecedent Context triple: [Portuguese conquest of Malacca, hasPrecedent, Portuguese capture of Goa]
-
A.
hasCourtPrecedence
Indicates that one court decision or ruling holds authoritative priority over another in legal reasoning or application.
-
B.
precedentFor
chosen
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
C.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
D.
hasPrecedentialStatus
Indicates that one legal decision or authority possesses a recognized level of precedential force or binding effect relative to others.
-
E.
typicalPrecedent
Indicates that one situation, case, or event serves as a standard or commonly followed example for how similar later situations are handled.
- 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.