Triple
T24212296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wall of Denial |
E600584
|
entity |
| Predicate | legalInFormat |
P35006
|
FINISHED |
| Object | Commander |
—
|
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: Commander | Statement: [Wall of Denial, legalInFormat, Commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalInFormat Context triple: [Wall of Denial, legalInFormat, Commander]
-
A.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
B.
legalLicenseIn
Indicates that an entity holds a valid legal license or authorization to operate, practice, or conduct a specified activity within a particular jurisdiction or region.
-
C.
legalEmbodimentOf
Indicates that one entity serves as the legally recognized form, vehicle, or representation through which another entity exists, acts, or holds rights and obligations in law.
-
D.
legalAuthorityIn
Indicates that an entity holds official legal power, jurisdiction, or governing authority within a specified area or domain.
-
E.
meetsFormat
chosen
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820401bc81909ae1837b41c85526 |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:55 p.m.