Triple
T25508730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stella |
E639313
|
entity |
| Predicate | occupiesFunction |
P159767
|
FINISHED |
| Object | source of poetic inspiration |
—
|
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: source of poetic inspiration | Statement: [Stella, occupiesFunction, source of poetic inspiration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupiesFunction Context triple: [Stella, occupiesFunction, source of poetic inspiration]
-
A.
occupiesFunction
chosen
Indicates that an entity performs, fills, or serves in a particular role, position, or functional capacity within a system or context.
-
B.
occupies
Indicates that one entity takes up or resides within a physical or conceptual space belonging to or associated with another entity.
-
C.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
D.
occupiesBlock
Indicates that one entity is physically positioned within or taking up space in a specified block or bounded area.
-
E.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 2:48 p.m.