Triple
T10163034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornelius |
E233935
|
entity |
| Predicate | genderOfNomen |
P3087
|
FINISHED |
| Object | masculine |
—
|
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: masculine | Statement: [Cornelius, genderOfNomen, masculine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderOfNomen Context triple: [Cornelius, genderOfNomen, masculine]
-
A.
genderSignificance
Indicates the relevance or impact that an entity’s gender has within a particular context, relationship, or interpretation.
-
B.
hasGrammaticalGender
chosen
Indicates that one entity assigns or possesses a specific grammatical gender in relation to another entity (such as a word, phrase, or linguistic unit).
-
C.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
D.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
E.
genderImplication
Indicates that one entity’s gender suggests, constrains, or determines the possible or likely gender of another entity.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5b5194819095645e9174897b0f |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.