Triple
T1883191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marie-Louise |
E39898
|
entity |
| Predicate | typicalBearers |
P34346
|
FINISHED |
| Object | women |
—
|
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: women | Statement: [Marie-Louise, typicalBearers, women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBearers Context triple: [Marie-Louise, typicalBearers, women]
-
A.
hasNotableFieldOfBearers
Indicates that the entities share a significant or distinguished area of activity, expertise, or achievement associated with their bearers.
-
B.
hasStandardBearer
Indicates that one entity serves as the official flag- or standard-carrier for another entity, typically in a ceremonial, military, or representative capacity.
-
C.
hasNotableBearer
Indicates that an entity (such as a name, title, or identifier) is borne by at least one notable person or entity.
-
D.
bearer
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
-
E.
bearerField
Indicates that one entity serves as the bearer or holder of a specific field, attribute, or property associated with 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb4f3fb9481908b54506dc2836124 |
completed | March 7, 2026, 5:17 a.m. |
Created at: March 4, 2026, 7:34 p.m.