Triple
T34886995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scout Borromeo Street |
E1006172
|
entity |
| Predicate | namedAfterClass |
P63
|
FINISHED |
| Object | Boy Scouts |
E1795849
|
NE 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: Boy Scouts | Statement: [Scout Borromeo Street, namedAfterClass, Boy Scouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterClass Context triple: [Scout Borromeo Street, namedAfterClass, Boy Scouts]
-
A.
classAfter
Indicates that one class or course occurs later in time or sequence than another class or course.
-
B.
namedAfterInstanceOf
Indicates that one entity is named after another entity that is an instance of a particular class or type.
-
C.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
D.
namedAfterPattern
Indicates that one entity’s name is derived from or follows the naming convention or pattern established by another entity.
-
E.
namedAfterField
Indicates that one entity has been given a name derived from or in honor of another entity, typically a person, place, or thing.
- F. None of above.
Provenance (4 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3786de303081909146f6e84160d67e |
completed | June 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4 p.m.