Triple
T30022239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Dodonna |
E762776
|
entity |
| Predicate | briefed |
P96146
|
FINISHED |
| Object | Red Squadron |
—
|
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: Red Squadron | Statement: [Jan Dodonna, briefed, Red Squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: briefed Context triple: [Jan Dodonna, briefed, Red Squadron]
-
A.
brieflyAttended
Indicates that an entity was present at or participated in another entity or event for only a short or limited duration.
-
B.
receivedIntelligenceBriefingsFrom
Indicates that one entity has been provided with intelligence briefings by another entity.
-
C.
usedBriefly
Indicates that an entity made short-term or momentary use of another entity or resource.
-
D.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
E.
providedInformationOn
chosen
Indicates that one entity supplied or communicated specific information or details to another entity.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679a7eb208190a85a8e61f45ba832 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:47 p.m.