Triple
T25582263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walk East on Beacon |
E641278
|
entity |
| Predicate | hasFBICooperation |
P158871
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Walk East on Beacon, hasFBICooperation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFBICooperation Context triple: [Walk East on Beacon, hasFBICooperation, true]
-
A.
hasFacebookAccount
Indicates that an entity possesses or maintains a Facebook account.
-
B.
hasSocialService
Indicates that an entity provides, offers, or is associated with a social service to another entity or community.
-
C.
hasSocialNetworkingIntegration
Indicates that an entity is connected to or supports interaction with one or more social networking platforms.
-
D.
hasNetworkPartner
Indicates that an entity is connected to another entity through a formal or recognized network partnership relationship.
-
E.
hasCooperative
Indicates that one entity participates in a cooperative relationship or partnership with another entity.
- F. None of above. chosen
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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f93653948190baf191db01add4b2 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 4:13 p.m.