Triple
T26129307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overfalls Foundation |
E659191
|
entity |
| Predicate | usesAsResource |
P2506
|
FINISHED |
| Object | Lightship Overfalls |
—
|
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: Lightship Overfalls | Statement: [Overfalls Foundation, usesAsResource, Lightship Overfalls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAsResource Context triple: [Overfalls Foundation, usesAsResource, Lightship Overfalls]
-
A.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
-
B.
isUsedAs
chosen
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
usesExternalResources
Indicates that an entity relies on or interacts with resources that originate outside of itself or its immediate system.
-
D.
usesResourceSeparation
Indicates that one entity applies or enforces a separation of resources between entities or processes, preventing them from sharing or interfering with each other’s resources.
-
E.
usedAsSourceIn
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 8:13 p.m.