Triple
T33557306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evan Wright (character) |
E859513
|
entity |
| Predicate | embeddedWith |
P176884
|
FINISHED |
| Object | 1st Reconnaissance Battalion |
—
|
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: 1st Reconnaissance Battalion | Statement: [Evan Wright (character), embeddedWith, 1st Reconnaissance Battalion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embeddedWith Context triple: [Evan Wright (character), embeddedWith, 1st Reconnaissance Battalion]
-
A.
canBeEmbeddedIn
Indicates that one entity can be inserted or integrated within another entity, typically preserving structure or compatibility.
-
B.
inlaidWith
Indicates that one object has decorative material set into its surface, typically flush with it, using a contrasting substance or pattern.
-
C.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
incorporatedBy
Indicates that an entity was formally created, organized, or established as a legal corporation by another entity.
- F. None of above. chosen
Provenance (4 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:40 a.m.