Triple
T3140619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monroe Doctrine |
E65635
|
entity |
| Predicate | notFormally |
P13450
|
FINISHED |
| Object | treaty |
—
|
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: treaty | Statement: [Monroe Doctrine, notFormally, treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notFormally Context triple: [Monroe Doctrine, notFormally, treaty]
-
A.
notTypically
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
-
B.
notOfficialNameOf
chosen
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
-
C.
hasInformalStatus
Indicates that an entity holds a non-official, casual, or unofficial standing or role in relation to another entity.
-
D.
notFullyIncorporated
Indicates that one entity has not been completely integrated, absorbed, or merged into another entity or system.
-
E.
nonConstructive
Indicates that the relationship or action does not provide a direct, explicit method or example to realize or build the object, outcome, or proof it asserts exists.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada57743e08190a1069c62e32f1bd4 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.