Triple
T19487353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosie |
E487544
|
entity |
| Predicate | canBeUsedIndependently |
P64000
|
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: [Rosie, canBeUsedIndependently, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedIndependently Context triple: [Rosie, canBeUsedIndependently, true]
-
A.
canBeUsedWithout
chosen
Indicates that one entity is capable of functioning or being utilized independently of another specified entity.
-
B.
worksIndependentlyOf
Indicates that one entity performs its function or activity without relying on, being influenced by, or requiring coordination with another entity.
-
C.
hasIndependent
Indicates that one entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
D.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
-
E.
cannotBeUsedWithout
Indicates that one entity is dependent on another such that it cannot function, operate, or be utilized unless the other entity is also present or in use.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63441434081909bf26259bab677fe |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.