Triple
T37077655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girl Scout Promise |
E917754
|
entity |
| Predicate | allowsSubstitutionFor |
P28179
|
FINISHED |
| Object | word "God" |
—
|
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: word "God" | Statement: [Girl Scout Promise, allowsSubstitutionFor, word "God"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsSubstitutionFor Context triple: [Girl Scout Promise, allowsSubstitutionFor, word "God"]
-
A.
involvesSubstitute
Indicates that one entity participates in a situation, event, or role as a replacement or stand-in for another entity.
-
B.
hasSubstitutionsType
Indicates that an entity is associated with a specific kind or category of substitutions applied to it or occurring within it.
-
C.
numberOfSubstitutes
Indicates the quantity of substitute entities associated with or allowed for a given entity or situation.
-
D.
mayBeReplacedBy
chosen
Indicates that one entity can potentially be substituted or superseded by another entity.
-
E.
substitutionProcedure
Indicates a process in which one element, component, or entity is replaced with another according to specified rules or conditions.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:14 p.m.