Triple
T11046984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aman |
E261159
|
entity |
| Predicate | banOn |
P85525
|
FINISHED |
| Object | Mortal Men |
—
|
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: Mortal Men | Statement: [Aman, banOn, Mortal Men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: banOn Context triple: [Aman, banOn, Mortal Men]
-
A.
banType
Indicates the specific category or kind of prohibition or restriction that has been applied.
-
B.
bannedBy
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
C.
banExtended
Indicates that an existing ban on an entity is prolonged beyond its original duration or scope.
-
D.
bando
chosen
Indicates a relationship where an entity is placed under a ban, prohibition, or outlaw status imposed by some authority.
-
E.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798307da481908996557a73c9b49a |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.