Triple
T6849709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beryl |
E157983
|
entity |
| Predicate | moreCommonAs |
P72600
|
FINISHED |
| Object | female name |
—
|
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: female name | Statement: [Beryl, moreCommonAs, female name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moreCommonAs Context triple: [Beryl, moreCommonAs, female name]
-
A.
moreCommonIn
Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
-
B.
isLessCommonThan
Indicates that one item occurs, appears, or is observed less frequently than another item.
-
C.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
D.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
E.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84acb288190a67d974197ecab2f |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:20 p.m.