Triple
T176940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romance languages |
E3592
|
entity |
| Predicate | shareFeature |
P7447
|
FINISHED |
| Object | grammatical gender |
—
|
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: grammatical gender | Statement: [Romance languages, shareFeature, grammatical gender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareFeature Context triple: [Romance languages, shareFeature, grammatical gender]
-
A.
sharesPowerWith
Indicates that two or more entities jointly hold, exercise, or distribute authority or control in a shared manner.
-
B.
sharesHead
Indicates that two entities have the same head element, leader, or top-level component in common.
-
C.
sharesEventWith
Indicates that two entities participate in, are associated with, or are linked through the same event.
-
D.
sharesMarketWith
Indicates that two entities operate in or target the same market or customer segment, implying competitive or overlapping commercial presence.
-
E.
sharesRulesWith
Indicates that two entities follow, are governed by, or operate under the same set of rules or regulations.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258fd278481908ad4498e03f38e2f |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25669d99481908c5e82ba8641205a |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a258b30f6c8190be2181f30c40e04d |
completed | Feb. 28, 2026, 2:53 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.