Triple
T164337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woman Holding a Balance |
E2977
|
entity |
| Predicate | rights |
P5532
|
FINISHED |
| Object | public domain |
—
|
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: public domain | Statement: [Woman Holding a Balance, rights, public domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rights Context triple: [Woman Holding a Balance, rights, public domain]
-
A.
license
Indicates that one entity has granted another entity formal permission or authorization to use, perform, or exploit something under specified terms.
-
B.
restriction
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
-
C.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
D.
authority
Indicates that one entity has the power, right, or official capacity to direct, control, or make decisions for another entity or over a particular domain.
-
E.
legalSubject
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258827da481909b20ea5e9d21676f |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2566392208190a538ea9aa1fac53e |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257101060819094db0f3a3a72f312 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.