Triple
T30307534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keichō Embassy to Europe |
E770825
|
entity |
| Predicate | includedEnvoy |
P114345
|
FINISHED |
| Object | Luis Sotelo |
—
|
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: Luis Sotelo | Statement: [Keichō Embassy to Europe, includedEnvoy, Luis Sotelo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedEnvoy Context triple: [Keichō Embassy to Europe, includedEnvoy, Luis Sotelo]
-
A.
hasEnvoy
chosen
Indicates that one entity serves as an official representative, delegate, or envoy acting on behalf of another entity.
-
B.
receivedEnvoyFrom
Indicates that one entity formally accepted or hosted an envoy or diplomatic representative sent by another entity.
-
C.
hasEnvoi
Indicates that one entity includes or is associated with an envoi, typically a concluding or dedicatory section appended to a main text or composition.
-
D.
launchEnvelope
Indicates initiating the sending or dispatching of an item or message, typically by packaging it into an envelope and starting its delivery process.
-
E.
supportsEnvironment
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a006fe981488190b4287289a3327664 |
completed | May 10, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_6a006f6976ec8190ba2c04fbaa946345 |
completed | May 10, 2026, 11:43 a.m. |
Created at: April 29, 2026, 7:49 p.m.