Triple
T1256780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Woman's Worth |
E12410
|
entity |
| Predicate | hasHook |
P24936
|
FINISHED |
| Object | "Cause a real man knows a real woman’s worth" |
—
|
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: "Cause a real man knows a real woman’s worth" | Statement: [A Woman's Worth, hasHook, "Cause a real man knows a real woman’s worth"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHook Context triple: [A Woman's Worth, hasHook, "Cause a real man knows a real woman’s worth"]
-
A.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
B.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
C.
hasHubFunction
Indicates that an entity serves as a central hub or coordinating point for certain activities, connections, or functions within a system.
-
D.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
E.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfa8cfa08190ac49c437a94a843c |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc4a1f048190bd1ddcc4cc3fe057 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:50 p.m.