Triple
T18772783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbig Ae/Be stars |
E459056
|
entity |
| Predicate | stillContracting |
P132918
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Herbig Ae/Be stars, stillContracting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillContracting Context triple: [Herbig Ae/Be stars, stillContracting, true]
-
A.
reasonForContraction
Indicates that one event, condition, or factor serves as the cause or explanation for a contraction (such as a reduction, tightening, or shrinking) in something.
-
B.
developmentalContractedWith
Indicates a formal developmental agreement or contract established between two entities, typically for research, design, or product development activities.
-
C.
resultOfLabor
Indicates that something exists or occurs as the outcome or product of someone’s work or effort.
-
D.
stillInvolvedIn
Indicates that an entity continues to participate in or be associated with a particular activity, role, or relationship at the present time.
-
E.
usesConstriction
Indicates that one entity applies pressure by tightening or squeezing around another entity to restrain, control, or affect it.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e593378a4081909cc1b0856fce7d7d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.