Triple
T20223416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosalind and Orlando |
E495315
|
entity |
| Predicate | notableDeviceInCourtship |
P139289
|
FINISHED |
| Object | cross-dressing |
—
|
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: cross-dressing | Statement: [Rosalind and Orlando, notableDeviceInCourtship, cross-dressing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDeviceInCourtship Context triple: [Rosalind and Orlando, notableDeviceInCourtship, cross-dressing]
-
A.
notableCourt
Indicates that a particular court is especially significant or noteworthy in relation to the subject.
-
B.
notableDeviceLine
Indicates that a device is a prominent or well-known product line associated with an entity.
-
C.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
D.
notableCouple
Indicates that two entities are widely recognized or documented as a couple in a notable or significant relationship.
-
E.
notableCircuit
Indicates that an entity is recognized as a significant or noteworthy circuit, such as an important electrical, racing, or logical circuit.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd827708190b798a30f4e7d533f |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:39 p.m.