Triple
T32645760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seeonee wolf pack |
E834591
|
entity |
| Predicate | ultimatelyAccepts |
P125252
|
FINISHED |
| Object | Mowgli as pack member |
—
|
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: Mowgli as pack member | Statement: [Seeonee wolf pack, ultimatelyAccepts, Mowgli as pack member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimatelyAccepts Context triple: [Seeonee wolf pack, ultimatelyAccepts, Mowgli as pack member]
-
A.
laterAccepts
chosen
Indicates that one entity accepts, approves, or agrees to something at a time subsequent to a referenced earlier point or event.
-
B.
acceptedFor
Indicates that one entity has been approved or admitted to receive, participate in, or be associated with another entity.
-
C.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
D.
hasAcceptance
Indicates that one entity has formally received, approved, or agreed to something offered, proposed, or requested by another entity.
-
E.
mandatedAcceptanceOf
Indicates that one entity is required, by rule or authority, to accept or approve something from 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c775d6188190b236fc4f89a11b61 |
completed | May 3, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:07 a.m.