Triple
T5320118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To injure no man, but to bless all mankind |
E121650
|
entity |
| Predicate | scopeOfConcern |
P61710
|
FINISHED |
| Object | all mankind |
—
|
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: all mankind | Statement: [To injure no man, but to bless all mankind, scopeOfConcern, all mankind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfConcern Context triple: [To injure no man, but to bless all mankind, scopeOfConcern, all mankind]
-
A.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
-
B.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
C.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
D.
subjectMatterScope
Indicates the thematic or topical domain that an action, statement, or resource pertains to or falls within.
-
E.
scopeOfReference
chosen
Indicates the range or domain of things, concepts, or entities to which a reference, statement, or expression applies.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84561c7081909e5937c7816e492c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 1:59 p.m.