Triple
T34586194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Radley |
E888049
|
entity |
| Predicate | secretlyProtects |
P92725
|
FINISHED |
| Object | Scout Finch |
—
|
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: Scout Finch | Statement: [Arthur Radley, secretlyProtects, Scout Finch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretlyProtects Context triple: [Arthur Radley, secretlyProtects, Scout Finch]
-
A.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
B.
secretlyPreserves
Indicates that one entity preserves or maintains something related to another entity in a concealed or undisclosed manner.
-
C.
secretlyIs
Indicates that one entity possesses a hidden or undisclosed identity, role, or attribute in relation to another entity.
-
D.
secretedBy
Indicates that a substance or product is released or produced by a particular cell, tissue, organ, or organism.
-
E.
secretlyAssists
chosen
Indicates that one entity provides help or support to another without the knowledge of the recipient or relevant third parties.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.