Triple
T38422908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikatuna |
E903278
|
entity |
| Predicate | treatyRitual |
P20718
|
FINISHED |
| Object | blood compact |
—
|
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: blood compact | Statement: [Sikatuna, treatyRitual, blood compact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyRitual Context triple: [Sikatuna, treatyRitual, blood compact]
-
A.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
-
B.
treatyAfter
Indicates that a treaty or formal agreement was established after a specified prior event, condition, or relationship between the entities.
-
C.
signedTreatyAt
Indicates that an entity formally entered into and endorsed a treaty at a specific location.
-
D.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
E.
treatyType
chosen
Indicates the specific category or classification of a treaty that characterizes the nature of the agreement between parties.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:31 p.m.